maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Martin Höller (JIRA) <>
Subject [jira] Commented: (MECLIPSE-380) dependencies in multi-module may projects require a 'mvn install' before using
Date Tue, 06 May 2008 13:33:22 GMT


Martin Höller commented on MECLIPSE-380:

Alfie Kirkpatrick did some research on this and posted the results [here|,-multi-project-and-reactor-dependencies---a-bug--to13387970.html#a13388483].

It seems this issue is not related to MNG-2277 as Brian wrote, because MNG-2277 is closed
already but this problem still exists with maven 2.0.9 and maven-eclipse-plugin 2.5.1.

> dependencies in multi-module may projects require a 'mvn install' before using
> ------------------------------------------------------------------------------
>                 Key: MECLIPSE-380
>                 URL:
>             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

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message