What does mvn help:effective-pom say about the scope of those artifacts?

Wayne

On Wed, Jun 11, 2008 at 6:55 PM, Mick Knutson <[EMAIL PROTECTED]> wrote:
> I have these 3 dependencies that are still ending up in my war:
>
>        *<dependency>
>            <groupId>org.aspectj</groupId>
>            <artifactId>aspectjtools</artifactId>
>            <version>1.6.0</version>
>            <scope>provided</scope>
>        </dependency>
>
>        <dependency>
>            <groupId>org.aspectj</groupId>
>            <artifactId>aspectjweaver</artifactId>
>            <version>1.5.4</version>
>            <scope>provided</scope>
>        </dependency>
>
>        <dependency>
>            <groupId>org.aspectj</groupId>
>            <artifactId>aspectjweaver</artifactId>
>            <version>1.6.0</version>
>            <scope>provided</scope>
>        </dependency>*
>
> Why am I not allowed to scope these top provided so they are not in my war?
> My war is >45MB and need to slim it down.
>
>
> --
> ---
> Thank You…
>
> Mick Knutson
> BASE Logic, inc.
>
> Website: http://baselogic.com
> Blog: http://baselogic.com/blog
> BLiNC Magazine: http://blincmagazine.com
> Linked IN: http://linkedin.com/in/mickknutson
> DJ Mick: http://djmick.com
> MySpace: http://myspace.com/mickknutson
> Tahoe: http://tahoe.baselogic.com
>

Reply via email to