We (the dev team) know this annoying bug but we don't have yet found a fix.
I'm not sure we'll be able to fix it for 2.5. Nicolas ?
I'm not sure that there's an issue opened for it. If you can check.
Arnaud
On Feb 1, 2008 9:22 AM, Martin H=F6ller <martin@xss.co.at> wrote:
> Hi all!
>
> I have an issue with the m-eclipse-p and a multi-module prject. 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.
>
> Am I missing something here?
> Is there an oportunity to tell maven to skip dependency checking?
>
> regards,
> - martin
> --
> Martin H=F6ller | martin.hoeller@xss.co.at
> *x Software + Systeme | http://www.xss.co.at/
> Karmarschgasse 51/2/20 | Tel: +43-1-6060114-30
> A-1100 Vienna, Austria | Fax: +43-1-6060114-71
>
--=20
..........................................................
Arnaud HERITIER
..........................................................
OCTO Technology - aheritier AT octo DOT com
www.octo.com | blog.octo.com
..........................................................
ASF - aheritier AT apache DOT org
www.apache.org | maven.apache.org
...........................................................
|