If you state a dependency directly in your POM, then the scope you set (even if determined by dependency managmeent) will override any broader scopes specified by transitive dependencies.
So, you if you declare a junit dependency with test scope, that should overrride any other scope set by other depenencies. Same thing for things that should be set to provided. Additionally, you can, of course, exclude those dependencies entirely with the exclusions element. -Stephen On 1/10/06, Kees de Kooter <[EMAIL PROTECTED]> wrote: > I am packaging a war and amazingly it twice as large in size compared > to the old ant build. I notice a couple of things: > > 1. a lot of jars (e.g. junit) are being packaged that really should > only have provided or test scope. The reason is that some poms forgot > to give junit test scope. > 2. a lot of jars are present with different versions > > I would like to be *in charge* here. How can I set the actual scope of > jars and how can I rule out different versions of jars? > > thanx > > -- > Kees de Kooter > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Stephen Duncan Jr www.stephenduncanjr.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
