Details
-
Type:
Improvement
-
Status:
Closed
-
Priority:
Major
-
Resolution: Duplicate
-
Affects Version/s: 2.4, 2.5
-
Fix Version/s: None
-
Labels:None
-
Environment:Maven 2.0.8
-
Number of attachments :
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
| This issue duplicates: | ||||
| MNG-3283 | Plugins that require dependency resolution in early phases cause dependency resolution issue |
|
|
|
| This issue is depended upon by: | ||||
| MENFORCER-42 | Maven-Enforcer-Plugin fails in multimodule project when artifacts not in repository |
|
|
|
Alfie Kirkpatrick did some research on this and posted the results here.
It seems this issue is not related to
MNG-2277as Brian wrote, becauseMNG-2277is closed already but this problem still exists with maven 2.0.9 and maven-eclipse-plugin 2.5.1.MNG-2277as Brian wrote, becauseMNG-2277is closed already but this problem still exists with maven 2.0.9 and maven-eclipse-plugin 2.5.1.