Here's my dependency tree:
[INFO] [dependency:tree]
[INFO] de.mycompany.myproject:war:2.3.1
[INFO] +- junit:junit:jar:3.8.1:test (scope not updated to compile)
[INFO] +- de.mycompany:myproject2:jar:1.1.5:compile
[INFO] | \- commons-digester:commons-digester:jar:1.6:compile
[EMAIL PROTECTED] wrote:
Here's my dependency tree:
[INFO] +- org.openlaszlo:openlaszlo:pom:3.2:compile
[INFO] | +- axis:axis:jar:1.4:runtime (version managed from 1.2.1; scope
managed from compile)
[INFO] | | \-
Well, that's not really an option, as Openlazlo needs axis.
However, on the web, I found:
Congratulations, you've run into the Maven Suicide Bug. Sometimes, maven
downloads something which it shouldn't and afterwards, it suddenly is unable
to resolve version, dependencies, whatever.
[EMAIL PROTECTED] wrote:
Well, that's not really an option, as Openlazlo needs axis.
Yes, should have mentioned that: of course you declare the correct
versions of the excluded dependencies (axis etc.) again in your own pom.
Glad to hear you found another solution, though!
Stefan
--
Add the exclusion to openlaszlo and then ADD BACK the axis:axis
dependency manually in your own pom with whatever version you want to
use.
Wayne
On 3/13/08, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Well, that's not really an option, as Openlazlo needs axis.
However, on the web, I found:
Perhaps some other dependency wants another version? Try putting it back
without the brackets and run dependency:tree to see what you get.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 12, 2008 11:14 AM
To: users@maven.apache.org
Subject:
Perhaps some other dependency wants another version? Try putting it back
without the brackets and run dependency:tree to see what you get.
Good point, will check that asap (when at work) - but even if -
if I tell Maven that it MUST use Version xy, shouldn't it behave as it was
told?!
Also,
: Wednesday, March 12, 2008 4:20 PM
To: Maven Users List
Subject: Re: RE: Version Range Specification
Perhaps some other dependency wants another version? Try putting it back
without the brackets and run dependency:tree to see what you get.
Good point, will check that asap (when at work) - but even
