Option to rely on transitive dependencies
-----------------------------------------
Key: MECLIPSE-370
URL: http://jira.codehaus.org/browse/MECLIPSE-370
Project: Maven 2.x Eclipse Plugin
Issue Type: New Feature
Components: Dependencies resolution and build path
Affects Versions: 2.4
Reporter: Ben Peacock
The generated .classpath file contains all transitive dependencies of a
project. It is impossible to tell within Eclipse which dependencies are the
immediate dependencies, without examining the pom.xml.
With a large number of projects and a deep dependency tree, dependencies of a
low-level project are duplicated in many other project classpaths. If I want to
test a change to these dependencies, I cannot just change the low-level
project's build path in Eclipse and see what happens, I have to change the
pom.xml and regenerate all the other Eclipse projects.
I would like an option for the .classpath to contain only the immediate
dependencies of a project, i.e. those explicit in the project's pom.xml, marked
as exported if the scope is not provided or test. This would keep each Eclipse
project classpath as simple as its pom.xml, making it easy to see and change
the dependency tree within Eclipse.
--
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
