Re: AW: [mvn] bad artifacs returned
Using an old copy of the libraries should work for you. (I have packaged the following dependencies: * jargs:jargs:1.0 * org.apache.xalan:xalan:2.7.1 * org.opensaml:openws:1.2.2) it applies to compile axis2:1.6.0 _m2_repo.rar http://maven.40175.n5.nabble.com/file/n5733969/_m2_repo.rar -- View this message in context: http://maven.40175.n5.nabble.com/mvn-bad-artifacs-returned-tp5712981p5733969.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: AW: [mvn] bad artifacs returned
Perso, I would do the opposite exclusions as AFAIK xalan artifacts
from xalan:xalan comes from apache folks.
dependency
groupIdorg.apache.ws.security/groupId
artifactIdwss4j/artifactId
version${wss4j.version}/version
exclusions
exclusion
artifactIdorg.apache.xalan/artifactId
groupIdxalan/groupId
/exclusion
/exclusions
/dependency
dependency
groupIdxalan/groupId
artifactIdxalan/artifactId
version2.7.1/version
/dependency
But that's my POV :-)
2012/7/5 Stadelmann Josef josef.stadelm...@axa-winterthur.ch:
Wayne,
the rampart-project.pom has the following.
!-- Other Rampart Dependencies --
dependency
groupIdorg.apache.ws.security/groupId
artifactIdwss4j/artifactId
version${wss4j.version}/version
exclusions
!-- We exclude xalan:xalan as a transitive dependency, but
include
org.apache.xalan:xalan as a direct dependency. This
avoids
conflicts with the dependencies of org.opensaml:opensaml
(which uses org.apache.xalan:xalan). --
to say is this is only true for opensaml-2.3.3 but not for opensaml-2.5.1
exclusion
artifactIdxalan/artifactId
groupIdxalan/groupId
/exclusion
/exclusions
/dependency
dependency
groupIdorg.apache.xalan/groupId
artifactIdxalan/artifactId
version2.7.1/version
/dependency
Josef
-Ursprüngliche Nachricht-
Von: Stadelmann Josef [mailto:josef.stadelm...@axa-winterthur.ch]
Gesendet: Donnerstag, 5. Juli 2012 10:08
An: Maven Users List; rwhee...@artifact-software.com
Betreff: AW: AW: [mvn] bad artifacs returned
Wayne
the answer is simple; look at
http://search.maven.org/remotecontent?filepath=org/opensaml/opensaml/2.2.3/opensaml-2.2.3.pom
and see how opensaml's dependency on xalan is defined.
That is to say if I get you right :::
if I have a dependency on opensaml I need to exclude in my project the
transitive dependency to xalan in the dependency to opensaml?
Josef
-Ursprüngliche Nachricht-
Von: Ron Wheeler [mailto:rwhee...@artifact-software.com]
Gesendet: Mittwoch, 4. Juli 2012 17:36
An: users@maven.apache.org
Betreff: Re: AW: [mvn] bad artifacs returned
It appears you have a bad dependency definition.
Only you can fix it.
The right one is
dependency
groupIdxalan/groupId
artifactIdxalan/artifactId
version2.7.1/version
/dependency
It appears that you have
dependency
groupIdorg.apache.xalan/groupId
artifactIdxalan/artifactId
version2.7.1/version
/dependency
No one knows how you got this included in your effective POM but it is
wrong.
Excluding all the repos in the world will not fix your problem.
Ron
On 04/07/2012 10:46 AM, Stadelmann Josef wrote:
that is what I want to tell you that you will not find any artifacy at
-Ursprüngliche Nachricht-
Von: Olivier Lamy [mailto:ol...@apache.org]
Gesendet: Mittwoch, 4. Juli 2012 16:37
An: Maven Users List
Betreff: Re: [mvn] bad artifacs returned
AFAIK xalan has the groupId:artifactId xalan:xalan see
http://repo.maven.apache.org/maven2/xalan/xalan/
Maybe you declare the repository
http://shibboleth.internet2.edu/downloads/maven2 in your pom (or in a
project you are using)
2012/7/4 Stadelmann Josef josef.stadelm...@axa-winterthur.ch:
what is returned to an depencey invoked artifact download
if the link to the artifact does not hit a .pom or the .jar wanted
but is redirected by the receiving repository server to a basic
html page explaing the user that artifacts have been moved?
i.e. currently for
/org/apache/xalan/xalan/2.7.1/xalan-2.7.1.jar
/org/opensaml/openws/1.2.2/openws-1.2.2.jar;
jargs/jargs/1.0/jargs-1.0.jar
i.e. beeing requested to download from
Downloading:
http://repo1.maven.org/maven2/org/apache/xalan/xalan/2.7.1/xalan-2.7.1.p
om
but is then redirected to
Downloading:
http://shibboleth.internet2.edu/downloads/maven2/org/apache/xalan/xalan/
2.7.1/xalan-2.7.1.pom
where it ends in the nirvana as this EP is redirected
http://shibboleth.internet2.edu/ explaing that stuuf has been moved.
Josef
--
Ron Wheeler
President
Artifact Software Inc
email: rwhee...@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h
Re: AW: [mvn] bad artifacs returned
I think that I pointed this out several days ago.
We always check the full list of dependencies including the transitive
ones in our projects to ensure that we are aware of version issues.
Our repo setup also restricts the places that Maven can ook for artifacts.
Ron
On 05/07/2012 4:41 AM, Olivier Lamy wrote:
Perso, I would do the opposite exclusions as AFAIK xalan artifacts
from xalan:xalan comes from apache folks.
dependency
groupIdorg.apache.ws.security/groupId
artifactIdwss4j/artifactId
version${wss4j.version}/version
exclusions
exclusion
artifactIdorg.apache.xalan/artifactId
groupIdxalan/groupId
/exclusion
/exclusions
/dependency
dependency
groupIdxalan/groupId
artifactIdxalan/artifactId
version2.7.1/version
/dependency
But that's my POV :-)
2012/7/5 Stadelmann Josef josef.stadelm...@axa-winterthur.ch:
Wayne,
the rampart-project.pom has the following.
!-- Other Rampart Dependencies --
dependency
groupIdorg.apache.ws.security/groupId
artifactIdwss4j/artifactId
version${wss4j.version}/version
exclusions
!-- We exclude xalan:xalan as a transitive dependency, but
include
org.apache.xalan:xalan as a direct dependency. This avoids
conflicts with the dependencies of org.opensaml:opensaml
(which uses org.apache.xalan:xalan). --
to say is this is only true for opensaml-2.3.3 but not for opensaml-2.5.1
exclusion
artifactIdxalan/artifactId
groupIdxalan/groupId
/exclusion
/exclusions
/dependency
dependency
groupIdorg.apache.xalan/groupId
artifactIdxalan/artifactId
version2.7.1/version
/dependency
Josef
-Ursprüngliche Nachricht-
Von: Stadelmann Josef [mailto:josef.stadelm...@axa-winterthur.ch]
Gesendet: Donnerstag, 5. Juli 2012 10:08
An: Maven Users List; rwhee...@artifact-software.com
Betreff: AW: AW: [mvn] bad artifacs returned
Wayne
the answer is simple; look at
http://search.maven.org/remotecontent?filepath=org/opensaml/opensaml/2.2.3/opensaml-2.2.3.pom
and see how opensaml's dependency on xalan is defined.
That is to say if I get you right :::
if I have a dependency on opensaml I need to exclude in my project the
transitive dependency to xalan in the dependency to opensaml?
Josef
-Ursprüngliche Nachricht-
Von: Ron Wheeler [mailto:rwhee...@artifact-software.com]
Gesendet: Mittwoch, 4. Juli 2012 17:36
An: users@maven.apache.org
Betreff: Re: AW: [mvn] bad artifacs returned
It appears you have a bad dependency definition.
Only you can fix it.
The right one is
dependency
groupIdxalan/groupId
artifactIdxalan/artifactId
version2.7.1/version
/dependency
It appears that you have
dependency
groupIdorg.apache.xalan/groupId
artifactIdxalan/artifactId
version2.7.1/version
/dependency
No one knows how you got this included in your effective POM but it is
wrong.
Excluding all the repos in the world will not fix your problem.
Ron
On 04/07/2012 10:46 AM, Stadelmann Josef wrote:
that is what I want to tell you that you will not find any artifacy at
-Ursprüngliche Nachricht-
Von: Olivier Lamy [mailto:ol...@apache.org]
Gesendet: Mittwoch, 4. Juli 2012 16:37
An: Maven Users List
Betreff: Re: [mvn] bad artifacs returned
AFAIK xalan has the groupId:artifactId xalan:xalan see
http://repo.maven.apache.org/maven2/xalan/xalan/
Maybe you declare the repository
http://shibboleth.internet2.edu/downloads/maven2 in your pom (or in a
project you are using)
2012/7/4 Stadelmann Josef josef.stadelm...@axa-winterthur.ch:
what is returned to an depencey invoked artifact download
if the link to the artifact does not hit a .pom or the .jar wanted
but is redirected by the receiving repository server to a basic
html page explaing the user that artifacts have been moved?
i.e. currently for
/org/apache/xalan/xalan/2.7.1/xalan-2.7.1.jar
/org/opensaml/openws/1.2.2/openws-1.2.2.jar;
jargs/jargs/1.0/jargs-1.0.jar
i.e. beeing requested to download from
Downloading:
http://repo1.maven.org/maven2/org/apache/xalan/xalan/2.7.1/xalan-2.7.1.p
om
but is then redirected to
Downloading:
http://shibboleth.internet2.edu/downloads/maven2/org/apache/xalan/xalan/
2.7.1/xalan-2.7.1.pom
where it ends in the nirvana as this EP is redirected
http://shibboleth.internet2.edu/ explaing that stuuf has been moved.
Josef
--
Ron Wheeler
President
Artifact Software Inc
email: rwhee...@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
-
To unsubscribe, e-mail: users-unsubscr
Re: AW: [mvn] bad artifacs returned
It appears you have a bad dependency definition. Only you can fix it. The right one is dependency groupIdxalan/groupId artifactIdxalan/artifactId version2.7.1/version /dependency It appears that you have dependency groupIdorg.apache.xalan/groupId artifactIdxalan/artifactId version2.7.1/version /dependency No one knows how you got this included in your effective POM but it is wrong. Excluding all the repos in the world will not fix your problem. Ron On 04/07/2012 10:46 AM, Stadelmann Josef wrote: that is what I want to tell you that you will not find any artifacy at -Ursprüngliche Nachricht- Von: Olivier Lamy [mailto:ol...@apache.org] Gesendet: Mittwoch, 4. Juli 2012 16:37 An: Maven Users List Betreff: Re: [mvn] bad artifacs returned AFAIK xalan has the groupId:artifactId xalan:xalan see http://repo.maven.apache.org/maven2/xalan/xalan/ Maybe you declare the repository http://shibboleth.internet2.edu/downloads/maven2 in your pom (or in a project you are using) 2012/7/4 Stadelmann Josef josef.stadelm...@axa-winterthur.ch: what is returned to an depencey invoked artifact download if the link to the artifact does not hit a .pom or the .jar wanted but is redirected by the receiving repository server to a basic html page explaing the user that artifacts have been moved? i.e. currently for /org/apache/xalan/xalan/2.7.1/xalan-2.7.1.jar /org/opensaml/openws/1.2.2/openws-1.2.2.jar; jargs/jargs/1.0/jargs-1.0.jar i.e. beeing requested to download from Downloading: http://repo1.maven.org/maven2/org/apache/xalan/xalan/2.7.1/xalan-2.7.1.p om but is then redirected to Downloading: http://shibboleth.internet2.edu/downloads/maven2/org/apache/xalan/xalan/ 2.7.1/xalan-2.7.1.pom where it ends in the nirvana as this EP is redirected http://shibboleth.internet2.edu/ explaing that stuuf has been moved. Josef -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
