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/03 17:46:49 UTC
[mvn-3] jar files causing problems
Dear developer,
today I moved my project to a new machine.
I deleted my old maven repositor and I removed my mirrors from the
settings file to download the current valid pom and jar files into my
local repository
short after
$ mvn install
I could see the following
[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
[WARNING] The POM for org.opensaml:openws:jar:1.2.2 is invalid,
transitive dependencies (if any) will not be available, enable debug
logging for more details
[WARNING] The POM for jargs:jargs:jar:1.0 is invalid, transitive
dependencies (if any) will not be available, enable debug logging for
more details
[WARNING] The POM for org.apache.xerces:xml-apis:jar:2.9.1 is invalid,
transitive dependencies (if any) will not be available, enable debug
logging for more details
[WARNING] The POM for org.apache.xerces:xercesImpl:jar:2.9.1 is invalid,
transitive dependencies (if any) will not be available, enable debug
logging for more details
[WARNING] The POM for org.apache.xerces:resolver:jar:2.9.1 is invalid,
transitive dependencies (if any) will not be available, enable debug
logging for more details
[WARNING] The POM for org.apache.xerces:serializer:jar:2.9.1 is invalid,
transitive dependencies (if any) will not be available, enable debug
logging for more details
and later down after many successful download the install failed
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 46.761s
[INFO] Finished at: Tue Jul 03 17:11:53 CEST 2012
[INFO] Final Memory: 15M/490M
[INFO]
------------------------------------------------------------------------
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile
(default-compile) on project SpezplaService: Compilation failure:
Compilation failure:
[ERROR] error: error reading
/dka3/stadelma/.m2/repository/org/apache/xalan/xalan/2.7.1/xalan-2.7.1.j
ar; error in opening zip file
[ERROR] error: error reading
/dka3/stadelma/.m2/repository/org/opensaml/openws/1.2.2/openws-1.2.2.jar
; error in opening zip file
[ERROR] error: error reading
/dka3/stadelma/.m2/repository/jargs/jargs/1.0/jargs-1.0.jar; error in
opening zip file
As I am on a OpenVMS machine we have to check file attibutes more carful
if we move jar or zip files. But maven downloads them normally very OK.
so I set my default dir to the place in the repository where the jar
file is stored. Then I used a jar tf command to see its content list. If
that works normal I do not have more problems with a jar. Buit if that
fails I have a bad jar or bad file attributes set.
....
bash$ cd 2.7.1
bash$ ls
_maven.repositories xalan-2.7.1.jar.lastUpdated
xalan-2.7.1.pom.lastUpdated
xalan-2.7.1.jar xalan-2.7.1.pom
bash$ jar tf xalan-2.7.1.jar
0: jar
1: tf
2: xalan-2.7.1.jar
java.util.zip.ZipException: error in opening zip file
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.<init>(ZipFile.java:114)
at java.util.zip.ZipFile.<init>(ZipFile.java:75)
at sun.tools.jar.Main.list(Main.java:979)
at sun.tools.jar.Main.run(Main.java:224)
at sun.tools.jar.Main.main(Main.java:1149)
bash$
I checked the file attributes but they are all OK. And I went to other
parts inj the reporitory and the just downloaded jar file all work and I
can retreive a content list using jar tf commands.
Any thougths how I can approach this problem is very welcome. Do others
have this problem too. How can I inspect or check consistency of a jar
file?
attached is a text file shwowing the full build unless it fails
Josef
<<JAR_problem.txt>>
Re: AW: [mvn-3] jar files causing problems
Posted by Jörg Schaible <Jo...@scalaris.com>.
Hi Josef,
Stadelmann Josef wrote:
> Ok Wayne
> or anybody else
[snip]
> 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
> <mirror><url>http://shibboleth.internet2.edu/downloads/maven2 ?
>
> can someone more fluent with that confirm or explain me what happens?
M2 has the unfortunate habbit to take repositories into account that are
somewhere declared in one of the POMs that are part of your build (i.e. also
those in transitive 3rd party POMs). That's the reason why it is discouraged
to declare repositories in POMs. Therefore your mirror declaration should
have a <mirrorOf>*</mirrorOf> entry to mask all those additional "injected"
repos. IIRC M3 behaves better, but uses such repos under some circumstances
also.
Regards,
Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
AW: [mvn-3] jar files causing problems
Posted by Stadelmann Josef <jo...@axa-winterthur.ch>.
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 <mirror><url>http://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:waynefay@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-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [mvn-3] jar files causing problems
Posted by Wayne Fay <wa...@gmail.com>.
> 100%-nail-hit! how did you know that
> xalan-2.7.1.jar & xalan-2.7.1.pom
> and other stuff . . .
> when downloaded as maven-artifact
> from the repository, comes down with
> such a bunch of HTML rubbish in it?
This is not entirely uncommon. I have seen it happen myself (from old
java.net repo, don't get me started). Since then, I am much more
careful about what mirrors I leverage in my builds and what repos we
connect to.
Wayne
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
AW: [mvn-3] jar files causing problems
Posted by Stadelmann Josef <jo...@axa-winterthur.ch>.
Wayne
100%-nail-hit! how did you know that
xalan-2.7.1.jar & xalan-2.7.1.pom
and other stuff . . .
when downloaded as maven-artifact
from the repository, comes down with
such a bunch of HTML rubbish in it?
Who deposits xalan-2.7.1.jar é all?
Before I deleted the mirrors in my
settings.xml, there was local company
repository mirror defined. This mirror
acts as proxy. And it provided me the
same rubbish. So I removed this mirror.
So the rubbish is located somehow central
and I wonder if I am the only one having
this types of troubles.
Below my settings.xml
Josef
<?xml version="1.0" encoding="ISO-8859-1"?>
<settings>
<localRepository>/dka3/stadelma/.m2/repository</localRepository>
<proxies>
<proxy>
<active>true</active>
<protocol>http</protocol>
<host>proxyserver.ch</host>
<port>8080</port>
<username>C770817</username>
<password>orbxorbx</password>
<nonProxyHosts>*.wgrintra.net</nonProxyHosts>
<id>default</id>
</proxy>
</proxies>
<mirrors>
</mirrors>
</settings>
I am going to move now, from my local PC m2/repository,
the failing artifacts into the OpenVMS m2/repository.
-----Ursprüngliche Nachricht-----
Von: Wayne Fay [mailto:waynefay@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-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [mvn-3] jar files causing problems
Posted by Wayne Fay <wa...@gmail.com>.
> [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-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org