| Summary: | Allow folding of libraries in Package Explorer view | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Daniel Dickman <didickman> |
| Component: | UI | Assignee: | JDT-UI-Inbox <jdt-ui-inbox> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | danny |
| Version: | 3.1 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Daniel Dickman
You could create a user library (Build Path -> Librararies -> Add Library, User Library) to contain all your archives. This would be shown in the package explorer as a single node with archives as children. The other possibility is to turn on/off the 'referenced libraries' filter in the package explorer. The third possiblity with 3.1 is to create two Java working sets: One with only the libraries and one with the rest. Then change to the working set mode of the package explorer. Reopened this one, because none of the options work for me. Rationale below. The user library option only lets me pick libraries from the file system. I want to be able to pick the jars from my project workspace instead. Turning on the 'referenced libraries' filter only hides the 'JRE System Library and any other libraries referenced from another project, but does not hide most of the libraries I'm looking at (they are under project/lib/*.jar and are not referenced from anywhere). For the third option, do you mean that I should create two separate projects, one of which contains only the libraries and the other of which contains the rest of the code? This wouldn't work well when we have some developers using unix and intellij in addition to eclipse. All I want is one node under my project called "Libraries" under which I'd have everything that is currently shown in: Properties -> Java Build Path -> Libraries and which I can expand or fold at will. can't do for 3.1 Is there any chance of re-opening this fr the 3.2 timeframe? (Or 3.1.1 but I guess it's too late for that.) I also have lots of projects, each of which uses lots of JARs from <project>/lib/.../*.jar, and would like to hide them, or fold them under an additional tree node. An alternative solution would be to allow project-level libraries which can include JAR files relative to the project, rather than absolute file-system paths. |