PROTECTED]
Sent: Thursday, October 05, 2006 11:34 PM
To: Maven Users List
Subject: RE: [M2] Overriding the Central Repository not working
Anyway Arnaud Bailly was right I have solved my problem by
creating a Bash script moving all the
maven-metadata-central.xml to maven-metdata.xml
-
From: Arnaud Bailly [mailto:[EMAIL PROTECTED]
Sent: Wednesday, 4 October 2006 5:43 PM
To: Maven Users List
Subject: Re: [M2] Overriding the Central Repository not working
Peter Anning [EMAIL PROTECTED] writes:
Hi,
Hello,
I do a build with a vanilla settings.xml
To: Maven Users List
Subject: RE: [M2] Overriding the Central Repository not working
Anyway Arnaud Bailly was right I have solved my problem by creating a Bash
script moving all the maven-metadata-central.xml to maven-metdata.xml
regenerating the sha1 files and delete al unwanted maven-metadata-*.xml
files
Bailly [mailto:[EMAIL PROTECTED]
Sent: Wednesday, 4 October 2006 5:43 PM
To: Maven Users List
Subject: Re: [M2] Overriding the Central Repository not working
Peter Anning [EMAIL PROTECTED] writes:
Hi,
Hello,
I do a build with a vanilla settings.xml add any stuff I need to my
Peter Anning [EMAIL PROTECTED] writes:
Hi,
Hello,
I do a build with a vanilla settings.xml add any stuff I need to my
local repository by hand. Then make a network copy of the local
repository delete my local repository and then my troubles start.
This won't work, AFAIK. There is
At first glance, those urls look completely wrong:
urlfile:///\\fileServer01/repository/url
Rather than playing with file:// until you make it work, can you
perhaps set up a simple Apache (or IIS) instance on top of the network
repo and use the standard HTTP:// reference to the repo? I'd
effect.
Peter
-Original Message-
From: Wayne Fay [mailto:[EMAIL PROTECTED]
Sent: Wednesday, 4 October 2006 2:49 PM
To: Maven Users List
Subject: Re: [M2] Overriding the Central Repository not working
At first glance, those urls look completely wrong:
urlfile:///\\fileServer01/repository
