EJ Ciramella wrote:
Still haven't seen any response - this has us wedged, can anyone shed
any light on this for me?
If you run "mvn <anything>" in some project/module subdirectory, you are
assuming that all dependencies are built and installed, and therefore
available either from your local repo, or from your other repositories.
If this is not true, then you cannot build.
If you are in the situation where "your" code builds, but "some else's"
code doesn't, then you won't be able to use your .ear file anyway. If
you don't need the .ear file yet, but do wish to run unit tests on
"your" code, then maybe you should temparily change your packaging to
"jar". If you want a more permanent solution, then make a separate
artifact which just has the dependencies to pack the ear, but no code
(except perhaps for some simple wrapping or debugging code) on its own...
But to me it sounds simply as if you'd want to run "mvn" from a higher
directory to get it to build all of your modules - or that you need to
ensure that the other people deploy the results of their builds.
--
cg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
