That is why one should not put repo definitions in poms.
The people at fault are the opensaml authors.
It is also why you mirror ALL references to repos that Maven makes so
that they all go to your repo manager and then your repo manager will
decide what external repos should be consulted.
That is your fault in this case.
BTW:
shibboleth.internet2.edu has no way to notify others who will be impacted by
their shutdown.
Perhaps they did notify you when they did it years ago but you did not
understand how that would affect you until this week.
OTOH: I sure hope Sonatype never shuts down Maven Central without sending me an
e-mail.
Sonantype guys, just to let you know... I really depend on Maven Central being
up.
Was I wrong about the dependency definition being incorrect?
Ron
On 04/07/2012 12:09 PM, Stadelmann Josef wrote:
And opensaml-2.2.3.pom has a reference as well
<repositories>
<repository>
<id>shibboleth.internet2.edu</id>
<name>Internet2</name>
<layout>default</layout>
<url>http://shibboleth.internet2.edu/downloads/maven2</url>
<snapshots>
<enabled>false</enabled>
</snapshots>
</repository>
</repositories>
Just to become aware that this url is outdated and leads to troubles with maven
when used in a download.
Don't ask me about the mystery when this will happen.
Josef
-----Ursprüngliche Nachricht-----
Von: Ron Wheeler [mailto:[email protected]]
Gesendet: Mittwoch, 4. Juli 2012 17:36
An: [email protected]
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>
<groupId>xalan</groupId>
<artifactId>xalan</artifactId>
<version>2.7.1</version>
</dependency>
It appears that you have
<dependency>
<groupId>org.apache.xalan</groupId>
<artifactId>xalan</artifactId>
<version>2.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:[email protected]]
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 <[email protected]>:
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: [email protected]
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
