[
http://jira.codehaus.org/browse/MECLIPSE-380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Höller closed MECLIPSE-380.
----------------------------------
Resolution: Duplicate
This issue is a duplicate of MNG-3283
> dependencies in multi-module may projects require a 'mvn install' before using
> ------------------------------------------------------------------------------
>
> Key: MECLIPSE-380
> URL: http://jira.codehaus.org/browse/MECLIPSE-380
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Improvement
> Components: Core : Dependencies resolution and build path, Core :
> Multi-projects
> Affects Versions: 2.4, 2.5
> Environment: Maven 2.0.8
> Reporter: Martin Höller
>
> 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
--
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
