Community
Participate
Working Groups
It should be possible to create a user library in a Java project as a file (just like the launch configurations). This would allow to keep them under version control and share the correct version between members of a team. Maybe you can put the project specific User Libraries in the .preferences folder so they don't clutter the normal project tree?
Exactly, it would be quite useful for projects sharing (we don't really use workspace sharing) especially with the automatic build machine...
got my vote
I would like to point out that a user library allows the exact contents of the library to be different from machine to machine. Hence if two people store their libraries in different folders, a project-specific user library will actually break their configurations. Individual JAR's on the build path will functionally accomplish what you are looking for, albeit without grouping the JAR's together.
Well, I could group the JARs by putting them into a project, set them to "exported" and then add that project to my build path. As for the "exact version", there are two solutions: 1. Always use the version number in the file name (i.e. "name-1.3.jar" instead of "name.jar") 2. Have Eclipse calculate a checksum of the library and add a warning to the project when the version doesn't match.
I may have misunderstood the original intent of the bug. If the purpose is to keep libraries under version control, you could keep your user library folder under version control, and have each developer build his user library against that checked out folder. Disadvantage: If a jar version/name changes, then upon updating the folder that contains the JAR's of the user library, the developers will have to fix the user library. At least eclipse will let you know about it...
*** Bug 270733 has been marked as a duplicate of this bug. ***
I don't think we should do anything here. From bug 270733: > Of course this can be emulated by substituting a Java project as a User > library, but that is a bit of an overkill for this. That's exactly the way to go. User libraries are meant for situations where each user has different library locations and the only thing that can be shared is the name of the library. If you know the exact paths to the JARs / class folders, then the right solution is a library project that can be shared.
