Re: Compilation failure due to looking at installed artifact instead for in project

2009-10-14 Thread Ren
Hello Stephen, I have a similar problem and still couldn't resolve. My project has three sub modules: war, ear, and lib, both war and ear depend on lib. I made a parent project to include all three modules. (A very typical setup I guess). When I want to build just ear, I uses mvn package -pl

Re: Compilation failure due to looking at installed artifact instead for in project

2009-10-14 Thread Ren
Hi Stephen, I think I just figured out myself. I have use the -am argument. So it's like: mvn package -am -pl ear Cheers Ren On Wed, Oct 14, 2009 at 5:38 PM, Ren rens...@gmail.com wrote: Hello Stephen, I have a similar problem and still couldn't resolve. My project has three sub modules:

Re: Compilation failure due to looking at installed artifact instead for in project

2009-10-14 Thread Stephen Connolly
2009/10/14 Ren rens...@gmail.com Hello Stephen, I have a similar problem and still couldn't resolve. My project has three sub modules: war, ear, and lib, both war and ear depend on lib. I made a parent project to include all three modules. (A very typical setup I guess). When I want to

Compilation failure due to looking at installed artifact instead for in project

2009-09-09 Thread Thomas Jonsson
Hi! I was just wondering if have misunderstood the basics of Maven and dependencies. I have a project according to this structure: ear ejbs core integration webapps webapp integration is dependent on core. from pom in integration.xml: dependency

Re: Compilation failure due to looking at installed artifact instead for in project

2009-09-09 Thread Anders Hammar
I guess you're building from the 'integration' project, not the aggregating project (ejbs)? If that's the case, your scenario is the expected way for it to work. Your dependency is to an artifact (the built jar), not a Maven project on your local disk. So you need to build the core project first.

Re: Compilation failure due to looking at installed artifact instead for in project

2009-09-09 Thread Thomas Jonsson
Hi! No, I'm buiding from project root. I just tested with Maven 2.0.10 with no compilation failures. But if I remove the core articfact from local repo it complains about it's missing. /Thomas 2009/9/9 Anders Hammar and...@hammar.net: I guess you're building from the 'integration' project,

Re: Compilation failure due to looking at installed artifact instead for in project

2009-09-09 Thread Stephen Connolly
you need to build at least as far as the package phase of the lifecycle... and you might even want to go as far as install... the jar file is not built until the package phase, so you will get these errors if you do not go as far as package.. also if you do builds of sub modules independently,

Re: Compilation failure due to looking at installed artifact instead for in project

2009-09-09 Thread Thomas Jonsson
Hi! Thanks for the explanation Stephen! /Thomas 2009/9/9 Stephen Connolly stephen.alan.conno...@gmail.com: you need to build at least as far as the package phase of the lifecycle... and you might even want to go as far as install... the jar file is not built until the package phase, so you