You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Ecker Severin <Se...@arcs.ac.at> on 2007/04/02 13:59:22 UTC
AW: Dependency version ignored
Hi,
I've just tried maven 2.0.6 with and without dependencyManagement, exclusions, no change.
Versions simply are ignored even though the dependency plugin resolves correctly.
Someone any more ideas?
Thanks in advance.
Cheers,
Severin
-----Ursprüngliche Nachricht-----
Von: Andrew Williams [mailto:andy@handyande.co.uk]
Gesendet: Dienstag, 27. März 2007 14:35
An: Maven Users List
Betreff: Re: AW: Dependency version ignored
use an <exclusion> on the xmlbeans dependency to stop junit from
being used?
in 2.0.6 dependencyManagement should sort this.
Andy
On 27 Mar 2007, at 08:07, Ecker Severin wrote:
> I'm trying once again...
>
> ----
>
> I'm not sure whether I'm not using dependencies correctly or this is a
> bug, but the situation is as follows:
>
> I have a junit 4.1 dependency in my project (and also xmlbeans).
> Now xmlbeans happens to have a dependency on junit 3.8.
>
> The problem is that my project uses junit 4 annotations BUT maven
> simply
> ignores my dependency and is totally content with junit3.8 on the
> classpath. Needless to say that the compilation fails.
>
> The funny thing though is if I run dependency:resolve immediately
> prior
> to compiler:testCompile it works just fine. (I suppose because
> xmlbeans
> is not used in the testCompile run).
>
> I'd appreciate any help on this.
>
> Thanks in advance,
> Severin
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Dependency version ignored
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
Can you give an example?
-----Original Message-----
From: Ecker Severin [mailto:Severin.Ecker@arcs.ac.at]
Sent: Monday, April 02, 2007 7:59 AM
To: Maven Users List
Subject: AW: Dependency version ignored
Hi,
I've just tried maven 2.0.6 with and without dependencyManagement, exclusions, no change.
Versions simply are ignored even though the dependency plugin resolves correctly.
Someone any more ideas?
Thanks in advance.
Cheers,
Severin
-----Ursprüngliche Nachricht-----
Von: Andrew Williams [mailto:andy@handyande.co.uk]
Gesendet: Dienstag, 27. März 2007 14:35
An: Maven Users List
Betreff: Re: AW: Dependency version ignored
use an <exclusion> on the xmlbeans dependency to stop junit from
being used?
in 2.0.6 dependencyManagement should sort this.
Andy
On 27 Mar 2007, at 08:07, Ecker Severin wrote:
> I'm trying once again...
>
> ----
>
> I'm not sure whether I'm not using dependencies correctly or this is a
> bug, but the situation is as follows:
>
> I have a junit 4.1 dependency in my project (and also xmlbeans).
> Now xmlbeans happens to have a dependency on junit 3.8.
>
> The problem is that my project uses junit 4 annotations BUT maven
> simply
> ignores my dependency and is totally content with junit3.8 on the
> classpath. Needless to say that the compilation fails.
>
> The funny thing though is if I run dependency:resolve immediately
> prior
> to compiler:testCompile it works just fine. (I suppose because
> xmlbeans
> is not used in the testCompile run).
>
> I'd appreciate any help on this.
>
> Thanks in advance,
> Severin
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org