|
| Re: How to export/import several projects at once [message #213362 is a reply to message #213174] |
Fri, 19 March 2004 08:15   |
Eclipse User |
|
|
|
Originally posted by: jon.homan.enigmatecNOSPAM.net
Oliver Plohmann wrote:
> Hello!
>
> I have an application that consists of several projects. Now I need to
> exchange the application with other people. Exporting all projects and
> importing them into a virgin eclipse system requires that all projects are
> first created manually (otherwise the import tool displays the error
> message "cannot import into a workspace with no open projects") and are
> then imported from the file system. This is a manual and tedious process
> which I want to get around. What I do at the moment to avoid this is to
> distribute the entire workspace and .config directory which is a brute
> force approach and not really satisfactory.
>
> Does anybody have an idea, has had this as well? I found a thread in the
> archive about Envy config maps for eclipse. Apparently, this discussion
> did not result in such a feature for eclipse.
>
> Thanx for any ideas,
> Oliver Plohmann
Do you have network access to the other developers? Using a CVS repository
is one way (you could set one up on your local machine), and then you just
export a Team Project Set (*.psf file) and email that to the developers.
They just import it and Eclipse handles setting up the repository
information and automatically checks out the projects.
You do not need to import the projects if they are valid Eclipse projects.
Unzip them into the target workspace and fire up the New Project wizard.
Just select the Simple -> Project and enter the Project name so that it is
the same as in the exported workspace. Press Finish and you will see the
projects in the Navigator. This works because Eclipse does not overwrite
the .project file. So even if the projects are plugin projects this method
should still work.
Regards,
Jon Homan
|
|
|
| Re: How to export/import several projects at once [message #213482 is a reply to message #213174] |
Fri, 19 March 2004 13:44 |
| Eclipse User |
|
|
|
Originally posted by: linnet.nospam.users.sourceforge.net
Hi Oliver,
I have made a plugin for this exact purpose. It can be installed from
the update site located at http://eclipse-tools.sourceforge.net/updates.
The name of the plugin is Project Transfer. If you don't want to use
the update manager you can just grab the jar file (at
http://eclipse-tools.sourceforge.net/updates/plugins/dk.kams truplinnet.projecttransfer_1.0.2.jar)
and install its contents manually.
There is currently absolutely no documentation whatsoever... Basically,
this is how it works:
- The plugin depends on the existence of .project and .classpath files
where the project should be created.
- Select Import... e.g. from the package explorer and choose "Existing
project definitions".
- Browse (or type) the root from where you want to search for existing
projects to import.
- Select "Next". You will now be presented with a list of the projects
found. Select the ones you want to import and press "Finish". Now, the
projects are (hopefully) imported.
Be aware the the error handling is very primitive. You may be presented
with an ugly dialog showing misc. errors. However, I haven't had
problems using it so far for my own purposes (such as making initial
Eclipse installations).
I am working on an "official" release at the moment, so stay tuned...
If you need assistance, feel free to contact me directly.
Best regards,
Jesper
Oliver Plohmann wrote:
> Hello!
>
> I have an application that consists of several projects. Now I need to
> exchange the application with other people. Exporting all projects and
> importing them into a virgin eclipse system requires that all projects are
> first created manually (otherwise the import tool displays the error message
> "cannot import into a workspace with no open projects") and are then
> imported from the file system. This is a manual and tedious process which I
> want to get around. What I do at the moment to avoid this is to distribute
> the entire workspace and .config directory which is a brute force approach
> and not really satisfactory.
>
> Does anybody have an idea, has had this as well? I found a thread in the
> archive about Envy config maps for eclipse. Apparently, this discussion did
> not result in such a feature for eclipse.
>
> Thanx for any ideas,
> Oliver Plohmann
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.02690 seconds
] 
Search
Help
Register
Login
Home
