Actually if you can track down where the unwanted dependencies are
coming from, you can add an excludes directly to that dependency node
to specifically exclude those artifacts.
For example, Ear depends on war, ejb, jar; war depends on logging;
thus logging ends up in EAR.
You should be able to exclude this via:
ear/pom.xml
<dependency>
<artifactId>war</>
<excludes>
<exclude>
<artifactId>logging</>
Wayne
On 10/26/06, Alexander Sack <[EMAIL PROTECTED]> wrote:
Thanks David, that's what I did. Its a little odd that you have duplicate
entries for the same dependency (btw, mvn shoots out warnings regarding
override scope, harmless I know, but still...).
-aps
On 10/26/06, David J. M. Karlsen <[EMAIL PROTECTED]> wrote:
>
> Alexander Sack wrote:
> > Because I'm using some of the Apache commons libraries, Maven2 is
> including
> > some of their sub dependencies such as commons-logging which breaks my
> EAR.
> > Is there a way to prevent this?
>
> Yes - declare it with scope provided.
>
> --
> David J. M. Karlsen - +47 90 68 22 43
> http://www.davidkarlsen.com
> http://mp3.davidkarlsen.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
"What lies behind us and what lies in front of us is of little concern to
what lies within us." -Ralph Waldo Emerson
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
