Multiproject dependency confusion/problem

["Poppe, Troy" <Tr...@eia.doe.gov>]

I have a fairly complex application that is composed of the following
'projects'/modules:

common - jar
client - jar
ejb - ejb
ejb-client - jar
ear - ear

I also have a 'root' project to assist eclipse.  This project contains a
project.xml with a bunch of shared attributes.  (groupId and currentVersion and
some dependencies, for example).  All the other 'projects' extend from this
project.xml.

The dependencies for my projects look something like this:

ejb depends ejb-client and common
ejb-client depends on common
common depends on nothing
client depends on ejb-client and common

I would assume that when I run any multiproject goal that the order of execution
would be:

common
ejb-client
client
ejb
ear

However, the order of execution ends up being:

common
client
ear
ejb
ejb-client

Obviously this breaks, as when multiproject gets to client, it cannot resolve the
dependency on ejb-client (unless there's a copy left over somewhere....)

Help?

Thanks.

Troy


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org