Likely because dependency plugin has bugs, and I'm suspecting that your
issue is similar/related to this
<>one already reported.

But it's odd that it doesn't fail for you at module mod_c, as build reactor
should have ordered mod_c to be built/processed before mod_d. Just guessing,
maybe this mojo doesn't use maven reactor at all, and probably mod_c is
ordered in list of modules in your parent module after mod_d.


On Wed, Nov 18, 2009 at 6:37 PM, Jonathan Gold <> wrote:

> Hi --
> I'm trying to track down some other depdendency issues in my project using
> dependencies:tree, but am getting errors that a module isn't found.
> I have my project set up with a parent pom and a list of modules, each
> referencing the parent, etc. Essentially, I have this:
>    pom.xml # parent, references mods a, b, c, d in <modules>
>    mod_a/pom.xml # module, no module dependencies
>    mod_b/pom.xml # module, no module dependencies
>    mod_c/pom.xml # module, declared dependency on mod_b
>    mod_d/pom.xml # module, declared depdenency on mod_a, mod_b, mod_c
> From the root workspace directory, I can run things like 'compile' or
> 'jar:jar'
> just fine, but for some reason 'dependencies:tree' is failing when it gets
> to
> mod_d, complaining that it can't find mod_c.
> Any ideas what I'm doing wrong?
> jon
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

Reply via email to