BRIAN FOX-5 wrote:
>
> can you send information about how
> you have Maven configured to use Nexus?
>
pretty much copied from the nexus documentation:
<mirrors>
<mirror>
<id>nexus</id>
<mirrorOf>*</mirrorOf>
<url>http://nexus.cor-fs.com/nexus/content/groups/BITA</url>
</mirror>
</mirrors>
<profiles>
<profile>
<id>nexus</id>
<!--Enable snapshots for the built in central repo to direct -->
<!--all requests to nexus via the mirror -->
<repositories>
<repository>
<id>central</id>
<url>http://central</url>
<releases>
<checksumPolicy>fail</checksumPolicy>
<enabled>true</enabled></releases>
<snapshots><enabled>true</enabled></snapshots>
</repository>
</repositories>
<pluginRepositories>
<pluginRepository>
<id>central</id>
<url>http://central</url>
<releases>
<checksumPolicy>fail</checksumPolicy>
<enabled>true</enabled>
</releases>
<snapshots><enabled>true</enabled></snapshots>
</pluginRepository>
</pluginRepositories>
We don't have a firewall or proxy, Nexus is on the LAN. However it is on a
different subnet, so it is going through a router.
Tracing route to nexus [10.0.1.124]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 10.0.6.1
2 12 ms <1 ms <1 ms nexus [10.0.1.124]
Trace complete.
The machine that works is on the 10.0.1.X subnet, so I am going to get my
machine on to that subnet and see if it works.
BRIAN FOX-5 wrote:
>
> I'd also like to see the files that were downloaded
> into your local repo (the jar and metadata, checksume etc.) assuming
> they are public.
>
http://www.nabble.com/file/p25039375/lucene-corrupted..zip
lucene-corrupted..zip
Attached is one of the corrupted jars (this was in
org\apache\lucene\lucene-core\2.4.0\lucene-core-2.4.0.jar) but contains
javax.xml.stream.
Thanks for your advice
David
--
View this message in context:
http://www.nabble.com/Jar-Contents-getting-mixed-up%21-tp25026781p25039375.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]