You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Stadelmann Josef <jo...@axa-winterthur.ch> on 2012/07/04 16:28:29 UTC
[mvn] bad artifacs returned
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
Re: [mvn] bad artifacs returned
Posted by Ron Wheeler <rw...@artifact-software.com>.
On 05/07/2012 11:02 AM, Wayne Fay wrote:
>> I am not sure I understand the reluctance to test that POMs are well-formed.
>> A POM that is not well-formed is worthy of a note at least.
> I just wouldn't want a not-well-formed pom (which Maven says is ok for
> its purposes) to prevent someone from being able to use a given
> artifact as a dependency. I agree that a well-formed test is
> reasonable for pom files but would want it to give a WARNING not an
> ERROR.
>
>> It should be possible to recognize the HTML returned by the "big-three"
>> repos in the case of an error and display the HTML body or part of it in the
>> error message.
> Which are the "big three"? ;-)
I am not sure but I drive a Nexus.:-)
>
>> Perhaps a standard could be agreed upon by the "big-three" to make it easier
>> for Maven to detect the fact that an error message has been returned and
>> have all three put out similar messages.
> I prefer webserver error messages to return the proper http status
> code as they should (*not* http 200), then we wouldn't even have this
> discussion.
Good start to a standard!
> Wayne
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
Ron Wheeler
President
Artifact Software Inc
email: rwheeler@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [mvn] bad artifacs returned
Posted by Wayne Fay <wa...@gmail.com>.
> I am not sure I understand the reluctance to test that POMs are well-formed.
> A POM that is not well-formed is worthy of a note at least.
I just wouldn't want a not-well-formed pom (which Maven says is ok for
its purposes) to prevent someone from being able to use a given
artifact as a dependency. I agree that a well-formed test is
reasonable for pom files but would want it to give a WARNING not an
ERROR.
> It should be possible to recognize the HTML returned by the "big-three"
> repos in the case of an error and display the HTML body or part of it in the
> error message.
Which are the "big three"? ;-)
> Perhaps a standard could be agreed upon by the "big-three" to make it easier
> for Maven to detect the fact that an error message has been returned and
> have all three put out similar messages.
I prefer webserver error messages to return the proper http status
code as they should (*not* http 200), then we wouldn't even have this
discussion.
Wayne
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [mvn] bad artifacs returned
Posted by Ron Wheeler <rw...@artifact-software.com>.
I am not sure I understand the reluctance to test that POMs are well-formed.
A POM that is not well-formed is worthy of a note at least.
Compared to the cost of a download, the test for well-formed XML should
be pretty small for a file the size of a POM.
It should be possible to recognize the HTML returned by the "big-three"
repos in the case of an error and display the HTML body or part of it in
the error message.
Perhaps a standard could be agreed upon by the "big-three" to make it
easier for Maven to detect the fact that an error message has been
returned and have all three put out similar messages.
Ron
On 04/07/2012 6:24 PM, Wayne Fay wrote:
>>>> Ideally there would be some Maven magic which checks the contents of
>>>> the file and ensures it seems like a reasonable pom, jar, war, etc
>>>> before saving it to the local repo cache but that does not currently
>>>> exist beyond a feature request in JIRA.
>> I think that the suggestion to validate items returned is a good one
>> that we should raise with, I think, Aether.
> I don't disagree. I'm not sure that we can guarantee much beyond "this
> seems to be XML" (I'm not sure that we should test for it being
> well-formed etc) or "this seems to be a zip file" (for jars, wars and
> ears) but just a basic check of "this is not garbage HTML" would be
> sufficient (and a big enhancement) for most users.
>
> Wayne
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
Ron Wheeler
President
Artifact Software Inc
email: rwheeler@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [mvn] bad artifacs returned
Posted by Wayne Fay <wa...@gmail.com>.
>>> Ideally there would be some Maven magic which checks the contents of
>>> the file and ensures it seems like a reasonable pom, jar, war, etc
>>> before saving it to the local repo cache but that does not currently
>>> exist beyond a feature request in JIRA.
> I think that the suggestion to validate items returned is a good one
> that we should raise with, I think, Aether.
I don't disagree. I'm not sure that we can guarantee much beyond "this
seems to be XML" (I'm not sure that we should test for it being
well-formed etc) or "this seems to be a zip file" (for jars, wars and
ears) but just a basic check of "this is not garbage HTML" would be
sufficient (and a big enhancement) for most users.
Wayne
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [mvn] bad artifacs returned
Posted by Benson Margulies <bi...@gmail.com>.
I think that the suggestion to validate items returned is a good one
that we should raise with, I think, Aether.
On Wed, Jul 4, 2012 at 2:38 PM, Ron Wheeler
<rw...@artifact-software.com> wrote:
> There should be a BIG note on the Maven front page and on the download page.
>
> "Do NOT even think about using Maven until you have your Maven repo running!
> This means you!!! When applied without a repo, Maven is hazardous and may
> cause rage, intense loathing of your vocation and a desire to kick an
> innocent person, animal or inanimate object or to write ill-tempered e-mail
> to forums.
> Seriously, you will not like the experience and you may get hurt and waste
> days.
> If anything does not work and you do not have a repo, you are on your own
> and will have to depend on the pity of strangers!"
>
>
> This whole problem would not even be in the forum if a repo had been
> installed.
>
> Ron
>
>
> On 04/07/2012 12:42 PM, Wayne Fay wrote:
>>>
>>> in fact content of any jar or pom or sha downloaded is the html page
>>> explaining the user that
>>>
>>> *** Internet2 Shibboleth Project has moved ***
>>>
>>> what is wrong ?
>>>
>>> who has to act ?
>>
>> This is the result of a poorly configured Maven repository. This is
>> not Maven's fault.
>>
>> The shibboleth repository should not return http 200 status code when
>> it is unable to serve the proper file, which is what it is doing.
>> Maven interprets the http 200 status code as "everything is OK" and
>> saves the resulting HTML as the pom or jar file you requested.
>>
>> Ideally there would be some Maven magic which checks the contents of
>> the file and ensures it seems like a reasonable pom, jar, war, etc
>> before saving it to the local repo cache but that does not currently
>> exist beyond a feature request in JIRA.
>>
>> Problems like this hopefully teach people to be aware of what Maven
>> repositories they are linking to for dependencies and become a little
>> bit more cautious about them. Also if you were running a proper MRM
>> like Nexus, this problem would be dealt with in the MRM. For the best
>> Maven-experience, you really need to be running an MRM.
>>
>> Wayne
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
>
> --
> Ron Wheeler
> President
> Artifact Software Inc
> email: rwheeler@artifact-software.com
> skype: ronaldmwheeler
> phone: 866-970-2435, ext 102
>
>
> ---------------------------------------------------------------------
> 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
Re: [mvn] bad artifacs returned
Posted by Ron Wheeler <rw...@artifact-software.com>.
On 05/07/2012 10:59 AM, Wayne Fay wrote:
>> Am I mistaken to think that a
>> <mirrorOf>*</mirrorOf>
>>
>> in my settings.xml will stop Maven from reaching a repo that someone defined
>> in a jar that I include as a dependency?
> Yes, this is correct/what you want if you are running a "corporate
> repo" and should prevent "leaks" by repos declared in various
> dependency pom files.
>
> There has been some discussion of changing Maven's code to ignore (or
> add an option to do so) repos declared in pom files like this. I am in
> support of such a change.
It does seem to be kind of a security risk to be able to sneak a repo
into someone's environment like that.
I am glad that you confirmed that a properly set up repo and
settings.xml prevents this from happening.
In Josef's case, it would have changed the error and depending on what
Maven says when it finds the repo in the dependency, he might still have
been misled into trying to find the mis-configured xalan dependency
which could have resulted in the same amount of frustration but directed
in a different way.
At least he would not have had a missing dependency rather than a file
that looked to be the right name but was just html.
There needs to a recognition on the part of the Maven development group
that although repositories are not part of the development scope, they
need to have a more prominent place in the Maven documentation.
My experience of getting a repo latter in the maven adoption cycle, has
really made me aware of how much harder it was for us to work with Maven
and really understand the Maven philosophy before we had the repo.
Ron
> Wayne
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
Ron Wheeler
President
Artifact Software Inc
email: rwheeler@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [mvn] bad artifacs returned
Posted by Wayne Fay <wa...@gmail.com>.
> Am I mistaken to think that a
> <mirrorOf>*</mirrorOf>
>
> in my settings.xml will stop Maven from reaching a repo that someone defined
> in a jar that I include as a dependency?
Yes, this is correct/what you want if you are running a "corporate
repo" and should prevent "leaks" by repos declared in various
dependency pom files.
There has been some discussion of changing Maven's code to ignore (or
add an option to do so) repos declared in pom files like this. I am in
support of such a change.
Wayne
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [mvn] bad artifacs returned
Posted by Ron Wheeler <rw...@artifact-software.com>.
Am I mistaken to think that a
<mirrors>
<mirror>
<!--This sends everything else to /public -->
<id>nexus</id>
<mirrorOf>*</mirrorOf>
<url>http://myRepoURL:8081/nexus/content/groups/public</url>
</mirror>
</mirrors>
in my settings.xml will stop Maven from reaching a repo that someone
defined in a jar that I include as a dependency?
I believe that this setting sucks up any attempt by Maven on the
developers workstation to reach any repo and forces it to mine.
I will defer to your superior knowledge of Maven and repos but this was
the belief that triggered my comments about the benefit of a properly
configured Maven and repo preventing the problem in this case.
Am I wrong in thinking that I am safe from third party libraries
interfering with my master plan of library reference?
Ron
On 04/07/2012 4:36 PM, Wayne Fay wrote:
>> This whole problem would not even be in the forum if a repo had been
>> installed.
> Well, Josef did say in another post:
>>> we have a corporate repository acting as a proxy to central !
> ...
>>> But bad luck, our repository is really just a mirror of central and
>>> contains the same rubbish for xalan-2.7.1.pom and jar
> So it seems he does have some kind of a corporate repository which is
> acting as a proxy. I don't know any more details though (what MRM he
> is running, what version, how it is configured, etc) which might be
> helpful to know.
>
> Wayne
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
Ron Wheeler
President
Artifact Software Inc
email: rwheeler@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [mvn] bad artifacs returned
Posted by Wayne Fay <wa...@gmail.com>.
> This whole problem would not even be in the forum if a repo had been
> installed.
Well, Josef did say in another post:
>> we have a corporate repository acting as a proxy to central !
...
>> But bad luck, our repository is really just a mirror of central and
>> contains the same rubbish for xalan-2.7.1.pom and jar
So it seems he does have some kind of a corporate repository which is
acting as a proxy. I don't know any more details though (what MRM he
is running, what version, how it is configured, etc) which might be
helpful to know.
Wayne
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [mvn] bad artifacs returned
Posted by Ron Wheeler <rw...@artifact-software.com>.
There should be a BIG note on the Maven front page and on the download page.
"Do NOT even think about using Maven until you have your Maven repo running!
This means you!!! When applied without a repo, Maven is hazardous and
may cause rage, intense loathing of your vocation and a desire to kick
an innocent person, animal or inanimate object or to write ill-tempered
e-mail to forums.
Seriously, you will not like the experience and you may get hurt and
waste days.
If anything does not work and you do not have a repo, you are on your
own and will have to depend on the pity of strangers!"
This whole problem would not even be in the forum if a repo had been
installed.
Ron
On 04/07/2012 12:42 PM, Wayne Fay wrote:
>> in fact content of any jar or pom or sha downloaded is the html page explaining the user that
>>
>> *** Internet2 Shibboleth Project has moved ***
>>
>> what is wrong ?
>>
>> who has to act ?
> This is the result of a poorly configured Maven repository. This is
> not Maven's fault.
>
> The shibboleth repository should not return http 200 status code when
> it is unable to serve the proper file, which is what it is doing.
> Maven interprets the http 200 status code as "everything is OK" and
> saves the resulting HTML as the pom or jar file you requested.
>
> Ideally there would be some Maven magic which checks the contents of
> the file and ensures it seems like a reasonable pom, jar, war, etc
> before saving it to the local repo cache but that does not currently
> exist beyond a feature request in JIRA.
>
> Problems like this hopefully teach people to be aware of what Maven
> repositories they are linking to for dependencies and become a little
> bit more cautious about them. Also if you were running a proper MRM
> like Nexus, this problem would be dealt with in the MRM. For the best
> Maven-experience, you really need to be running an MRM.
>
> Wayne
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
Ron Wheeler
President
Artifact Software Inc
email: rwheeler@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [mvn] bad artifacs returned
Posted by Wayne Fay <wa...@gmail.com>.
> in fact content of any jar or pom or sha downloaded is the html page explaining the user that
>
> *** Internet2 Shibboleth Project has moved ***
>
> what is wrong ?
>
> who has to act ?
This is the result of a poorly configured Maven repository. This is
not Maven's fault.
The shibboleth repository should not return http 200 status code when
it is unable to serve the proper file, which is what it is doing.
Maven interprets the http 200 status code as "everything is OK" and
saves the resulting HTML as the pom or jar file you requested.
Ideally there would be some Maven magic which checks the contents of
the file and ensures it seems like a reasonable pom, jar, war, etc
before saving it to the local repo cache but that does not currently
exist beyond a feature request in JIRA.
Problems like this hopefully teach people to be aware of what Maven
repositories they are linking to for dependencies and become a little
bit more cautious about them. Also if you were running a proper MRM
like Nexus, this problem would be dealt with in the MRM. For the best
Maven-experience, you really need to be running an MRM.
Wayne
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
AW: [mvn] bad artifacs returned
Posted by Stadelmann Josef <jo...@axa-winterthur.ch>.
To answer part of my question:
if a project has a dependency on xalan, and somehow maven-magic the artifact is said to be at
http://shibboleth.internet2.edu/downloads/maven2/org/apache/xalan/xalan/2.7.1/xalan-2.7.1.pom
however, there, a redirect happens, and the pom or the jar just ends in the following content/page
--------------------
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<title>Internet2 Shibboleth Project has moved</title>
<style type="text/css">
h3, h4 {margin-bottom:0;}
h3+p {margin-top:0;}
. . .
--------------------
in fact content of any jar or pom or sha downloaded is the html page explaining the user that
*** Internet2 Shibboleth Project has moved ***
what is wrong ?
who has to act ?
this for the xalan and maybe many other artifacts expected to be found at the
http://shibboleth.internet2.edu/downloads/maven2 repository server
Josef
-----Ursprüngliche Nachricht-----
Von: Stadelmann Josef [mailto:josef.stadelmann@axa-winterthur.ch]
Gesendet: Mittwoch, 4. Juli 2012 16:28
An: Maven Users List
Betreff: [mvn] bad artifacs returned
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.pom
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 stuff has been moved.
Josef
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
AW: AW: [mvn] bad artifacs returned
Posted by Stadelmann Josef <jo...@axa-winterthur.ch>.
Ron
I would not say that - because I just found out that the artifact
org/apache/rampart/rampart-project/1.6.2/rampart-project-1.6.1.pom
has the following snippet in it. AND
My project so far depends on this artifact and it comes from apache !
Now I will check if I can make it without this artifact.
rampart-project-1.6.1.pom
and rampart-1.6.2 as well
<repositories>
<repository>
<releases>
<enabled>true</enabled>
<updatePolicy>always</updatePolicy>
<checksumPolicy>warn</checksumPolicy>
</releases>
<snapshots>
<enabled>true</enabled>
<updatePolicy>never</updatePolicy>
<checksumPolicy>warn</checksumPolicy>
</snapshots>
<id>open-saml</id>
<name>OpenSAML</name>
<url>http://shibboleth.internet2.edu/downloads/maven2/</url>
</repository>
</repositories>
But the trouble makers are not at apache !
they are at EDU shibboleth which moved the artifact repository
potentially without telling axis2/rampart folk what they did.
what can maven do when a request for an artifact is re-directed into nirvana?
Josef
-----Ursprüngliche Nachricht-----
Von: Ron Wheeler [mailto:rwheeler@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>
<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:olamy@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 <jo...@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: rwheeler@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
---------------------------------------------------------------------
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
Re: AW: [mvn] bad artifacs returned
Posted by andhdo <an...@gmail.com>.
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-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: AW: [mvn] bad artifacs returned
Posted by Ron Wheeler <rw...@artifact-software.com>.
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>
> <groupId>org.apache.ws.security</groupId>
> <artifactId>wss4j</artifactId>
> <version>${wss4j.version}</version>
> <exclusions>
> <exclusion>
> <artifactId>org.apache.xalan</artifactId>
> <groupId>xalan</groupId>
> </exclusion>
> </exclusions>
> </dependency>
> <dependency>
> <groupId>xalan</groupId>
> <artifactId>xalan</artifactId>
> <version>2.7.1</version>
> </dependency>
>
> But that's my POV :-)
>
> 2012/7/5 Stadelmann Josef <jo...@axa-winterthur.ch>:
>> Wayne,
>> the rampart-project.pom has the following.
>>
>> <!-- Other Rampart Dependencies -->
>> <dependency>
>> <groupId>org.apache.ws.security</groupId>
>> <artifactId>wss4j</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>
>> <artifactId>xalan</artifactId>
>> <groupId>xalan</groupId>
>> </exclusion>
>> </exclusions>
>> </dependency>
>> <dependency>
>> <groupId>org.apache.xalan</groupId>
>> <artifactId>xalan</artifactId>
>> <version>2.7.1</version>
>> </dependency>
>>
>> Josef
>>
>>
>> -----Ursprüngliche Nachricht-----
>> Von: Stadelmann Josef [mailto:josef.stadelmann@axa-winterthur.ch]
>> Gesendet: Donnerstag, 5. Juli 2012 10:08
>> An: Maven Users List; rwheeler@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:rwheeler@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>
>> <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:olamy@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 <jo...@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: rwheeler@artifact-software.com
>> skype: ronaldmwheeler
>> phone: 866-970-2435, ext 102
>>
>>
>> ---------------------------------------------------------------------
>> 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
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>
>
--
Ron Wheeler
President
Artifact Software Inc
email: rwheeler@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: AW: [mvn] bad artifacs returned
Posted by Olivier Lamy <ol...@apache.org>.
Perso, I would do the opposite exclusions as AFAIK xalan artifacts
from xalan:xalan comes from apache folks.
<dependency>
<groupId>org.apache.ws.security</groupId>
<artifactId>wss4j</artifactId>
<version>${wss4j.version}</version>
<exclusions>
<exclusion>
<artifactId>org.apache.xalan</artifactId>
<groupId>xalan</groupId>
</exclusion>
</exclusions>
</dependency>
<dependency>
<groupId>xalan</groupId>
<artifactId>xalan</artifactId>
<version>2.7.1</version>
</dependency>
But that's my POV :-)
2012/7/5 Stadelmann Josef <jo...@axa-winterthur.ch>:
> Wayne,
> the rampart-project.pom has the following.
>
> <!-- Other Rampart Dependencies -->
> <dependency>
> <groupId>org.apache.ws.security</groupId>
> <artifactId>wss4j</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>
> <artifactId>xalan</artifactId>
> <groupId>xalan</groupId>
> </exclusion>
> </exclusions>
> </dependency>
> <dependency>
> <groupId>org.apache.xalan</groupId>
> <artifactId>xalan</artifactId>
> <version>2.7.1</version>
> </dependency>
>
> Josef
>
>
> -----Ursprüngliche Nachricht-----
> Von: Stadelmann Josef [mailto:josef.stadelmann@axa-winterthur.ch]
> Gesendet: Donnerstag, 5. Juli 2012 10:08
> An: Maven Users List; rwheeler@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:rwheeler@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>
> <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:olamy@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 <jo...@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: rwheeler@artifact-software.com
> skype: ronaldmwheeler
> phone: 866-970-2435, ext 102
>
>
> ---------------------------------------------------------------------
> 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
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
AW: AW: [mvn] bad artifacs returned
Posted by Stadelmann Josef <jo...@axa-winterthur.ch>.
Wayne,
the rampart-project.pom has the following.
<!-- Other Rampart Dependencies -->
<dependency>
<groupId>org.apache.ws.security</groupId>
<artifactId>wss4j</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>
<artifactId>xalan</artifactId>
<groupId>xalan</groupId>
</exclusion>
</exclusions>
</dependency>
<dependency>
<groupId>org.apache.xalan</groupId>
<artifactId>xalan</artifactId>
<version>2.7.1</version>
</dependency>
Josef
-----Ursprüngliche Nachricht-----
Von: Stadelmann Josef [mailto:josef.stadelmann@axa-winterthur.ch]
Gesendet: Donnerstag, 5. Juli 2012 10:08
An: Maven Users List; rwheeler@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:rwheeler@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>
<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:olamy@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 <jo...@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: rwheeler@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
---------------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
AW: AW: [mvn] bad artifacs returned
Posted by Stadelmann Josef <jo...@axa-winterthur.ch>.
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:rwheeler@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>
<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:olamy@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 <jo...@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: rwheeler@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
---------------------------------------------------------------------
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
Re: AW: AW: [mvn] bad artifacs returned
Posted by Ron Wheeler <rw...@artifact-software.com>.
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:rwheeler@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>
> <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:olamy@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 <jo...@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: rwheeler@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
AW: AW: [mvn] bad artifacs returned
Posted by Stadelmann Josef <jo...@axa-winterthur.ch>.
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:rwheeler@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>
<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:olamy@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 <jo...@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: rwheeler@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
---------------------------------------------------------------------
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
Re: AW: [mvn] bad artifacs returned
Posted by Ron Wheeler <rw...@artifact-software.com>.
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:olamy@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 <jo...@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: rwheeler@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [mvn] bad artifacs returned
Posted by Olivier Lamy <ol...@apache.org>.
so in such case a solution is to exclude org.apache.xalan:xalan from
the shibboleth artifact.
and add a dependency to xalan:xalan.
And contact those folks who publish bad poms.
2012/7/4 Stadelmann Josef <jo...@axa-winterthur.ch>:
> that is what I want to tell you that you will not find any artifacy at
>
> -----Ursprüngliche Nachricht-----
> Von: Olivier Lamy [mailto:olamy@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 <jo...@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
>
>
>
> --
> Olivier Lamy
> Talend: http://coders.talend.com
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>
> ---------------------------------------------------------------------
> 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
>
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
AW: [mvn] bad artifacs returned
Posted by Stadelmann Josef <jo...@axa-winterthur.ch>.
that is what I want to tell you that you will not find any artifacy at
-----Ursprüngliche Nachricht-----
Von: Olivier Lamy [mailto:olamy@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 <jo...@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
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
---------------------------------------------------------------------
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
Re: [mvn] bad artifacs returned
Posted by Olivier Lamy <ol...@apache.org>.
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 <jo...@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
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org