Ok Wayne
or anybody else
we have a corporate repository acting as a proxy to central !
fine - this safes you a lot bandwidth and us time.
But what shall I do if I get same rubbish from our repository as well as from
central when I ask for pom / jar? for an artifact?
I just cleared out my m2/repository and have all downloaded for a small axis2
project from our repository at axa-winterthur.
As xalan jars and pom's and others are in error, just rubbish HTML in it, I
expected our axa-winterthur repository is bad;
Hence I took out from settings.xml the mirror to our repository. Sso I work
without any mirror at the moment.
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
- HTML in a POM and in the jar's
while my $ mvn install
takes place I observer the following
[INFO]
[INFO] Building SpezplaService 1.6.1
[INFO]
Downloading:
http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-deploy-plugin/maven-metadata.xml
Downloaded:
http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-deploy-plugin/maven-metadata.xml
(614 B at 2.2 KB/sec)
Downloading:
http://repo1.maven.org/maven2/org/apache/xalan/xalan/2.7.1/xalan-2.7.1.pom
Downloading:
http://shibboleth.internet2.edu/downloads/maven2/org/apache/xalan/xalan/2.7.1/xalan-2.7.1.pom
[WARNING] Checksum validation failed, expected !DOCTYPE but is
2b52583a26dc455eebec16f29ab9480344f2c5a4 for
http://shibboleth.internet2.edu/downloads/maven2/org/apache/xalan/xalan/2.7.1/xalan-2.7.1.pom
[WARNING] Checksum validation failed, expected !DOCTYPE but is
2b52583a26dc455eebec16f29ab9480344f2c5a4 for
http://shibboleth.internet2.edu/downloads/maven2/org/apache/xalan/xalan/2.7.1/xalan-2.7.1.pom
let's take 1 by 1
Downloading:
http://shibboleth.internet2.edu/downloads/maven2/org/apache/xalan/xalan/2.7.1/xalan-2.7.1.pom
taking this URL into the browser brings you to the shibboleth site and it seems
that the expected repository has been relocated to somewhere else. I think,
maven cannot handle this bad redirection but sucks up the HTML rubbish instead
from this site for the artifacts wanted.
What I do not understand is, why xalan-* and a few other artifacts must come
down from http://shibboleth.internet2.edu/downloads/maven2/org/apache/
Where can I prevent this? can I? can I black-list proactively the
mirrorurlhttp://shibboleth.internet2.edu/downloads/maven2 ?
can someone more fluent with that confirm or explain me what happens?
any help welcome
Josef
-Ursprüngliche Nachricht-
Von: Wayne Fay [mailto:wayne...@gmail.com]
Gesendet: Dienstag, 3. Juli 2012 18:28
An: Maven Users List
Betreff: Re: [mvn-3] jar files causing problems
[WARNING] The POM for org.apache.xalan:xalan:jar:2.7.1 is invalid,
transitive dependencies (if any) will not be available, enable debug logging
for more details
Cat the jar file or open it in vi etc. I bet you see an HTTP 503 or a
404 or something other HTML in there instead of the proper binary jar
bits.
Most likely you have a problem in your settings.xml. Ideally you
should set up a proper local Maven Repository Manager (Nexus, Archiva,
Artifactory, etc) and leverage it for your jar access.
Wayne
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
