Hi Henrique,
On 24/04/2008, at 1:23 AM, Henrique Prange wrote:
On Wed, Apr 23, 2008 at 2:24 AM, Lachlan Deck
<[EMAIL PROTECTED]> wrote:
Okay - making progress...
If I create a maven-archetype-j2ee-simple, cd into the dir, comment
out the
site module from the parent pom and do 'mvn package' it all works
without
having to install the sub-modules.
However, with my structure it doesn't grab the jars from the sub-
modules
for the app - but complains that they're not installed. The app (with
packaging = woapplication) fails to build.
Does it fail because Maven cannot find a dependency? Or is it
another problem?
It fails saying that I should firstly download the dependency and
manually install it - but it's one of the modules in the project.
My tree is like this:
/pom.xml
/myframeworks
/myframeworks/moduleA
...
/app1/pom.xml
It's a similar structure to the j2ee-simple example.
What am I missing? What's the 'trick' for making this work?
Have you tried "mvn clean install" in the parent module? The package
goal doesn't install the jars into the your local repository.
I realise that it doesn't install stuff. But that's my point, the j2ee-
simple project (which also has sub-modules of modules) didn't need to
have the modules installed in order to simply do mvn package right out
of the box, so to speak.
I'm wondering why it's different here. I'm trying to get away from the
old woproject-ant based system where something has to be installed
first prior to be able to build the application for testing/deployment.
Have you declared the sub-module dependency in your application
pom.xml?
Yes.
with regards,
--
Lachlan Deck
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
