[MECLIPSE-370] Option to rely on transitive dependencies

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Auto Closed
• Affects Version/s: 2.4
• Component/s: Core : Dependencies resolution and build path (.classpath)
• Assignee: Unassigned
• Reporter: Ben Peacock
• Created: 18/Jan/08 04:00
• Updated: 06/Sep/15 20:44
• Resolved: 06/Sep/15 20:44

Description

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.

Issue Links

• relates to: MECLIPSE-170 Exports on classpath entries destroy the classpath
• relates to: MECLIPSE-249 Generated .classpath file misses exported=true for dependency libraries
• relates to: MECLIPSE-230 Classpath entries to be marked exported