-when a library has more items in library classpath them every item is listed
separately under the Libraries node
->it could be more useful/space saving to list the items under the library node(
like in the platform case (e.g. JDK 1.6))
This would really make sense. The current state, although it intended to make
the contents of the Libraries node simpler, actually causes more visual clutter
than a 1:1 mapping of libraries to nodes. Try e.g. adding to a project a few
libraries composed of many jar files, like Spring or Hibernate, and you will see.
Also, as the reporter points out, the current state is inconsistent with the JDK
node, and also with the Java EE platform node in the Java EE projects.
Tomasi, why did you move this to projects/libraries? It looks to me like an
issue in the projects types. Or do you plan to implement a support for the
Libraries node? ;-)
This deserves a higher priority IMHO, upgrading to P2.
We do need a generic Libraries node, I think.
*** Issue 104886 has been marked as a duplicate of this issue. ***