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:[email protected]]
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: [email protected]
For additional commands, e-mail: [email protected]
