[
http://jira.codehaus.org/browse/MECLIPSE-289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_101720
]
John Allen commented on MECLIPSE-289:
-------------------------------------
I gotta say this is a very good idea for reasons that go beyond screen clutter.
Using a container like this would give a very good indication to users of the
project that they, well the IDE actually, are not in control of the
dependencies listed within it and instead a third party, in our case Maven, is
the manager of those dependencies.
Plus of course seeing:
* JRE System Library
* Maven Dependencies
In my project explorer is much better than the 40 odd jars I have now :)
> classpath entries should be bundled within a container
> ------------------------------------------------------
>
> Key: MECLIPSE-289
> URL: http://jira.codehaus.org/browse/MECLIPSE-289
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Wish
> Reporter: Roman Cerny
> Priority: Minor
>
> to avoid multiple lines in the package explorer, it would be nice to add a
> container to the .classpath file, containing all the Maven2 dependencies.
> <classpathentry kind="con"
> path="org.maven.ide.eclipse.MAVEN2_CLASSPATH_CONTAINER"/>
> instead of adding each dependency separately, all dependencies would be added
> within this container.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
