There isn't actually a way to turn it off wholesale, but you can
exclude specific ones using <exclusions />:
<dependency>
<groupId>dom4j</groupId>
...
<exclusions>
<exclusion>
<groupId>jdbc</groupId>
<artifactId>jdbc</artifactId>
</exclusion>
...
</exclusions>
This should be considered a last resort - what really needs to happen
is for the dom4j metadata to be corrected. It in particular is well
known to be problematic.
You can file issues for other metadata at http://jira.codehaus.org/browse/MEV
We will be spending more time after the beta-1 release on cleaning up
the existing metadata.
- Brett
On 8/4/05, Ken Weiner <[EMAIL PROTECTED]> wrote:
> I am new to Maven 2 and am trying to understand currently, in alpha 3,
> how transitive dependencies are supposed to be working.
>
> If I want to include something like dom4j-1.6.jar, but none of the
> dom4j dependencies, in my project, how would I specify this in the
> pom? I tried the following, and since the dom4j pom has many
> dependencies listed in it, maven tries to grab them all and fails
> because many aren't available in the repositories.
>
> <dependency>
> <groupId>dom4j</groupId>
> <artifactId>dom4j</artifactId>
> <version>1.6</version>
> <scope>runtime</scope>
> </dependency>
>
> I don't know if I should be declaring something differently in my pom
> or in the dom4j pom.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
