Re: RE: Version Range Specification

2008-03-13 Thread Dooing
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

[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] |  |  \- axis:axis-jaxrpc:jar:1.4:runtime
[INFO] |  +- xmlrpc:xmlrpc:jar:1.2-b1:runtime
[INFO] |  +- xpp3:xpp3:jar:1.1.3.3:runtime (version managed from 1.1.3.4d_b4)
[INFO] |  +- commons-beanutils:commons-beanutils:jar:1.6.1:compile
[INFO] |  +- commons-httpclient:commons-httpclient:jar:3.0:runtime (version 
managed from 2.0-rc1; scope managed from runtime)


[INFO] |  +- commons-jexl:commons-jexl:jar:1.0-dev:runtime
[INFO] |  +- batik:batik-svggen:jar:1.0:runtime
[INFO] |  +- jython:jython:jar:2.1:runtime
[INFO] |  +- jakarta-regexp:jakarta-regexp:jar:1.4:runtime (version managed 
from 1.2)
[INFO] |  +- isorelax:isorelax:jar:1.0:runtime
[INFO] |  +- org.openlaszlo:openlaszlo-saxon:jar:6.5.3-lz-p1:compile
[INFO] |  +- org.openlaszlo:openlaszlo-swflib:jar:1.0:runtime
[INFO] |  +- org.openlaszlo:openlaszlo-thaiopensource-jing:jar:1.0:runtime
[INFO] |  \- org.openlaszlo:openlaszlo-lps:jar:3.2:compile
[INFO] +- org.springframework:spring:jar:1.2.3:compile
[INFO] +- commons-logging:commons-logging:jar:1.0.4:compile
[INFO] +- commons-configuration:commons-configuration:jar:1.3:compile
[INFO] |  +- commons-collections:commons-collections:jar:3.1:compile (version 
managed from 2.0)
[INFO] |  +- commons-logging:commons-logging-api:jar:1.0.4:compile
[INFO] |  +- commons-beanutils:commons-beanutils-core:jar:1.7.0:compile
[INFO] |  +- commons-codec:commons-codec:jar:1.3:compile
[INFO] |  +- commons-jxpath:commons-jxpath:jar:1.2:compile
[INFO] |  |  +- xerces:xerces:jar:1.2.3:compile
[INFO] |  |  \- ant:ant-optional:jar:1.5.1:compile
[INFO] |  +- xerces:xercesImpl:jar:2.8.1:compile (version managed from 2.2.1)
[INFO] |  +- xalan:xalan:jar:2.7.0:compile
[INFO] |  \- xml-apis:xml-apis:jar:1.0.b2:compile
[INFO] +- javax.transaction:jta:jar:1.1:runtime
[INFO] +- javax.servlet:servlet-api:jar:2.4-20040521:provided
[INFO] +- javax.xml:jaxrpc-api:jar:1.1:runtime
[INFO] +- org.springframework:spring-mock:jar:1.2.3:test
[INFO] |  +- org.springframework:spring-jdbc:jar:1.2.3:test
[INFO] |  |  +- org.springframework:spring-dao:jar:1.2.3:test
[INFO] |  |  |  \- jotm:jotm:jar:2.0.10:test
[INFO] |  |  | +- jotm:jotm_jrmp_stubs:jar:2.0.10:test
[INFO] |  |  | +- javax.resource:connector:jar:1.0:test
[INFO] |  |  | +- org.objectweb.carol:carol:jar:2.0.5:test
[INFO] |  |  | \- howl:howl-logger:jar:0.1.11:test
[INFO] |  |  +- org.springframework:spring-beans:jar:1.2.3:test
[INFO] |  |  |  +- org.springframework:spring-core:jar:1.2.3:test
[INFO] |  |  |  \- cglib:cglib:jar:2.1_2:test
[INFO] |  |  +- c3p0:c3p0:jar:0.9.0:test
[INFO] |  |  \- com.experlog:xapool:jar:1.5.0:test
[INFO] |  \- org.springframework:spring-web:jar:1.2.3:test
[INFO] | +- javax.faces:jsf-api:jar:1.1:test
[INFO] | +- javax.servlet:jsp-api:jar:2.0:test
[INFO] | +- org.springframework:spring-context:jar:1.2.3:test
[INFO] | |  +- org.springframework:spring-aop:jar:1.2.3:test
[INFO] | |  |  +- aopalliance:aopalliance:jar:1.0:test
[INFO] | |  |  +- commons-attributes:commons-attributes-api:jar:2.1:test
[INFO] | |  |  |  +- ant:ant:jar:1.6.2:test (version managed from 1.5)
[INFO] | |  |  |  \- qdox:qdox:jar:1.5:test
[INFO] | |  |  +- 
commons-attributes:commons-attributes-compiler:jar:2.1:test
[INFO] | |  |  |  \- com.sun:tools:jar:1.4.2:system
[INFO] | |  |  \- com.jamonapi:jamon:jar:1.0:test
[INFO] | |  +- velocity:velocity:jar:1.4:test
[INFO] | |  |  \- velocity:velocity-dep:jar:1.4:test
[INFO] | |  +- freemarker:freemarker:jar:2.3.3:test
[INFO] | |  \- jasperreports:jasperreports:jar:1.0.0:test
[INFO] | +- struts:struts:jar:1.2.7:compile (scope managed from test)
[INFO] | |  +- commons-chain:commons-chain:jar:1.0:compile
[INFO] | |  +- commons-fileupload:commons-fileupload:jar:1.0:compile
[INFO] | |  +- commons-validator:commons-validator:jar:1.3.1:compile 
(version managed from 1.1.4)
[INFO] | |  \- oro:oro:jar:2.0.8:compile
[INFO] | +- com.servlets:cos:jar:05Nov2002:test
[INFO] | +- taglibs:standard:jar:1.0.6:test
[INFO] | \- javax.servlet:jstl:jar:1.1.2:compile (version managed from 1.0; 
scope managed from test)
[INFO] +- commons-discovery:commons-discovery:jar:0.2:compile
[INFO] +- axis:axis-saaj:jar:1.2:compile
[INFO] +- axis:axis-wsdl4j:jar:1.5.1:compile
-

So it seems that the reason is:
[INFO] +- org.openlaszlo:openlaszlo:pom:3.2:compile
[INFO] |  +- axis:axis:jar:1.4:runtime (version managed from 1.2.1; scope 
managed from 

Re: Version Range Specification

2008-03-13 Thread VUB Stefan Seidel



[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] |  |  \- axis:axis-jaxrpc:jar:1.4:runtime
[INFO] |  +- xmlrpc:xmlrpc:jar:1.2-b1:runtime
[INFO] |  +- xpp3:xpp3:jar:1.1.3.3:runtime (version managed from 1.1.3.4d_b4)
[INFO] |  +- commons-beanutils:commons-beanutils:jar:1.6.1:compile
[INFO] |  +- commons-httpclient:commons-httpclient:jar:3.0:runtime (version 
managed from 2.0-rc1; scope managed from runtime)



Well, the easiest solution for now is to exclude tose dependencies from 
openlaszlo:

dependency
  groupIdorg.openlazslo/groupId
  artifactIdopenlaszo/artifactId
  version3.2/version
  exclusions
exclusion
  groupIdaxis/groupId
  artifactIdaxis/artifactId
/exclusion

 ...

Stefan
--
best regards,

Stefan Seidel
software developer

VUB Printmedia GmbH
Chopinstraße 4
D-04103 Leipzig
Germany
tel.+49 (341) 9 60 50 07
fax.+49 (341) 9 60 50 92
mail.   [EMAIL PROTECTED]
web.www.vub.de

HRB Köln 24015
UStID DE 122 649 251
GF Dr. Achim Preuss Neudorf,
Dr. Christian Preuss Neudorf

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Version Range Specification

2008-03-13 Thread Dooing
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.

Therefore, I renamed my repo and just fed it with files that were not on the 
web - and - magically - it works now!!! Really weird!

Stefanie
-- 
Psst! Geheimtipp: Online Games kostenlos spielen bei den GMX Free Games! 
http://games.entertainment.gmx.net/de/entertainment/games/free

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Version Range Specification

2008-03-13 Thread VUB Stefan Seidel

[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

--
best regards,

Stefan Seidel
software developer

VUB Printmedia GmbH
Chopinstraße 4
D-04103 Leipzig
Germany
tel.+49 (341) 9 60 50 07
fax.+49 (341) 9 60 50 92
mail.   [EMAIL PROTECTED]
web.www.vub.de

HRB Köln 24015
UStID DE 122 649 251
GF Dr. Achim Preuss Neudorf,
Dr. Christian Preuss Neudorf

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Version Range Specification

2008-03-13 Thread Wayne Fay
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:

 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.

 Therefore, I renamed my repo and just fed it with files that were not on the 
 web - and - magically - it works now!!! Really weird!

 Stefanie
 --
 Psst! Geheimtipp: Online Games kostenlos spielen bei den GMX Free Games!
 http://games.entertainment.gmx.net/de/entertainment/games/free

 -
 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]



RE: Version Range Specification

2008-03-12 Thread Brian E. Fox
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: Version Range Specification

Hi,

I've got a problem - one of my projects is using openlazlo 3.2 - which
stinks, as they MANUALLY changed dependencies, without any documentation
about this, and they don't even provide any maven poms :-(

However, we have to use it, and I am trying to get it to run using Maven
2.

For OpenLazlo, I manually created a pom and installed it into my local
repo. Along with other dependencies, it specifies:
dependency
groupIdcommons-httpclient/groupId
artifactIdcommons-httpclient/artifactId
version2.0-rc1/version
scoperuntime/scope
/dependency

For whatever reason, Maven 2.08 isn't very impressed by version 2.0-rc1,
and uses 3.0 instead. This however let's the openlazlo project fail. The
only configuration I was able to run was using version 2.0-rc1. 
So I read:
http://maven.apache.org/plugins/maven-enforcer-plugin/rules/versionRange
s.html

and accordingly changed the version to:[2.0-rc1].
Now Maven 2 is even more unhappy:
--
[INFO] Failed to resolve artifact.
No versions are present in the repository for the artifact with a range
[2.0-rc1,2.0-rc1]
  commons-httpclient:commons-httpclient:jar:null

from the specified remote repositories:
  central (http://repo1.maven.org/maven2),
...
--
But WHY? If you browse to: 
http://repo1.maven.org/maven2/commons-httpclient/commons-httpclient/2.0-
rc1/

You can see it's def. there!!!
Also, I've got this file in my local repository!!! :-(

Any idea whats wrong here?

Thanks in advance, your help rules! :-)

Cheers,

Stefanie
-- 
Psst! Geheimtipp: Online Games kostenlos spielen bei den GMX Free Games!

http://games.entertainment.gmx.net/de/entertainment/games/free

-
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]



Re: RE: Version Range Specification

2008-03-12 Thread Dooing
 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, why doesn't Maven accept the Syntax [2.0-rc1] - I also tried that for 
other dependencies, and it always said it couldn't find the version specified. 
Really strange!!! :-(

Stefanie
-- 
Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! 
Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: RE: Version Range Specification

2008-03-12 Thread Brian E. Fox
This may be a bug where it can't satisfy the locked down version for some 
reason and the error isn't telling you the right thing. Lets work through it to 
see why and then maybe a jira will come from it.

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
Sent: 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 if -
if I tell Maven that it MUST use Version xy, shouldn't it behave as it was 
told?!

Also, why doesn't Maven accept the Syntax [2.0-rc1] - I also tried that for 
other dependencies, and it always said it couldn't find the version specified. 
Really strange!!! :-(

Stefanie
-- 
Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! 
Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer

-
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]