Community
Participate
Working Groups
It would be nice if I could export a team project set that pointed at a particular repository, but used (and included) my local .classpath and .project xml files rather than any that might be checked in to the code repository. This would allow me to have a team project set defined for Struts and all of it's jakarta-commons dependencies without having to depend on the various projects including the .project and .classpath in the repo. Even if they did include the files they might refer to local jars whereas I might want project depencies on other projects in the set. It would be easier to convince open source projects to check in various team project set files for eclipse (that pointed to the latest code, or to the particular tags associated with a release) rather than have than have them check in .project and .classpath files which are necessary for a team project set to make setting up lots of different projects as easy as possible. Ideally a new Struts developer could import a team project set that pointed to head and everything would be set up, without struts and it's several dependencies having eclipse project files. A struts user could import a team project set that referenced the various tags associated with a particular release and then they could step through code when debugging a problem and step from struts to beanutils, etc.
That is an interesting idea. What you really want is that the project set becomes a set of locations plus an archive of local files. Importing the set would fetch the projects from the repository then extract the archive into the workspace. If you would like to contribute something that does this that would be great.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
