Hi Lakshman, We have a number of these files some are *-local.xml, some are *-ibiblio.xml, some are the name of the repo from setting.xml on dev machines.
I'm not an expert at this, and please excuse if I am stating the obvious, but did you try using -U switch? Kind regards, -- Marc -----Original Message----- From: Lakshman Srilakshmanan [mailto:[EMAIL PROTECTED] Sent: 25 August 2006 09:18 To: Maven Users List Subject: RE: [m2] copy of Central Repository Hi Marc, I did a full build on the box that hosts our internal repo, but as explained, it did not work for me. I have also explained, below, my finding why it did not work. Could you please confirm the name of the following files in your repository. a) maven-metadata*.xml b) maven-metadata*.xml.sha1 Is it possible you are still looking at the central server at http://repo1.maven.org/maven2 ?? Thanks Lakshman > -----Original Message----- > From: Marc L. Veary [mailto:[EMAIL PROTECTED] > Sent: Friday, 25 August 2006 5:40 PM > To: 'Maven Users List' > Subject: RE: [m2] copy of Central Repository > > Hi. > > We started using mvn deploy:deploy-file, but then realised that if we did a > full build on the box that hosts our internal repo - this would do the job - > and it does. > > However, I would like to know if there is a better or 'proper' solution to > this. > > Kind regards, > -- > Marc > > -----Original Message----- > From: Lakshman Srilakshmanan > [mailto:[EMAIL PROTECTED] > Sent: 25 August 2006 07:54 > To: Maven Users List > Subject: [m2] copy of Central Repository > > > Hi All, > > In maven 1.x I could execute maven once on a project and build my local > repository. I could then copy it on to my company's central server and > get all the developers to refer to this for updates. > > When I needed a new plugin or dependency, I could run maven 1.x against > ibiblio and follow the above process. > > The above strategy ensured that we had only the plugins & dependencies > we needed and not the whole central repository of 5G. I am not going > into the details of how I kept this up-to-date as it would side track > the main issue that I wish to discuss. > > > Now, in maven 2 I did the same process as described above. The build > started breaking, with errors such as -- plugin 'xxx' does not exist or > no valid version could be found --. > > Further investigation revealed this problem was due to two missing files > in my repository. > a) maven-metadata.xml > b) maven-metadata.xml.sha1 > > In my local repository these files are named as > a) maven-metadata-central.xml > b) maven-metadata-central.xml.sha1 > > so when I copied my local repository to my company's central repository > the above files caused the problem. > > When I renamed the files as required, maven 2 was happy and everything > started to work again. > > > So my question is, is there a easier way of getting the required > components from maven central repository copied to my company's central > server without having to take a full copy ? > > Well, an alternative is to create a script to traverse the repository > and rename the files as required. > > I would much appreciate to hear from anyone who has solved this problem > or is there a tool/process that I have overlooked. > > Thanks in advance > > Lakshman > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
