[MECLIPSE-380] dependencies in multi-module may projects require a 'mvn install' before using

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 2.4, 2.5
• Component/s: Core : Dependencies resolution and build path (.classpath), Core : Multi-projects
• Environment: Maven 2.0.8
• Assignee: Unassigned
• Reporter: Martin Höller
• Created: 01/Feb/08 02:59
• Updated: 05/Apr/15 23:50
• Resolved: 06/May/08 09:38

Description

The scenario is as follows:

Parent Project P

+-- Project A

`- Project B

B has a dependency on A (B requires A).

A user with an empty local repository cannot checkout the whole project and
run 'mvn eclipse:eclipse' due to unsatisfied dependencies. The build will
fail in Project B because Project A is missing from the repository.

A 'mvn install' has to be executed before (at least for Project A). But what
if the project is in a state where it doesn't compile? It's not possible in
this case for a new user to start developing with eclipse.

See also http://www.nabble.com/maven-eclipse-plugin-with-multi-module-projects-to15222495s177.html

Issue Links

• duplicates: MNG-3283 Plugins that require dependency resolution in early phases cause dependency resolution issue
• is depended upon by: MENFORCER-42 Maven-Enforcer-Plugin fails in multimodule project when artifacts not in repository