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 Thomas Jonsson
it will be handled correctly. Or you use some tool to help you (m2eclipse). If you find yourself updating updating two different projects, then your separation might not be right. /Anders On Wed, Sep 9, 2009 at 09:17, Thomas Jonsson jonsson.tho...@gmail.comwrote: Hi! I was just wondering if have

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

2009-09-09 Thread Thomas Jonsson
build will not have access to the artifact.  going as far as install will push the reactor artifacts into the local repository, which then makes the artifacts available to subsequent maven invokations -Stephen 2009/9/9 Thomas Jonsson jonsson.tho...@gmail.com Hi! No, I'm buiding from project

Add directory to the classpath

2008-10-08 Thread Thomas Jonsson
Hi! Is it possible to add a directory to the classpath with maven? To make the directory as a jar artifact is not an option. The background is that I'm managing a seam project using maven, and in the test phase, a bootstrap directory must be on the classpath , otherwise the jboss embedded