Jesse,
Thanks much, that was exactly what was happening. I added
dependency scoping to the pom for all the jars that the war was
depending on, and then they stopped coming through to the war.
A caveat, I expected the dependency scoping to be able to be placed in a
parent pom, but this does not seem to be the case.
Michael D. Cassidy
Software Architect
Vegas.com
[EMAIL PROTECTED]
-----Original Message-----
From: Jesse McConnell [mailto:[EMAIL PROTECTED]
Sent: Friday, September 02, 2005 12:54 PM
To: Maven Users List
Subject: Re: FW: [m2] war plug-in does not pay attention to dependency
scoping
are you certain that you are not bringing in the dependency from another
one that you are sucking into the war?
use -X to get a breakdown of the dependency tree and maybe even paste
that into here...
On 9/2/05, Michael Cassidy <[EMAIL PROTECTED]> wrote:
>
> > I am using m2 (alpha2-3) to build a war. I have included scoping
> > information on dependencies, but they still end up in the war.
> > Anyone have an idea how to fix this. Pom excerpt below...
> >
> > <dependency>
> > <groupId>tomcat-common-lib</groupId>
> > <artifactId>_env-sb-concierge-tomcat</artifactId>
> > <version>0.0</version>
> > <scope>provided</scope>
> > </dependency>
> >
> >
> > Michael D. Cassidy
> > Software Architect
> > Vegas.com <http://Vegas.com>
> > [EMAIL PROTECTED]
> >
>
>
--
jesse mcconnell
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
