I asked the same question on the maven mailing list and I got the following answer:
"Yes, first local and remote maven repository doesn't contain the same metadata. And by the way, accessing a local repository by many instances isn't concurrent-safe (at least, in maven 2, I don't know precisely what's been done for maven 3, particularly along the parallel build evolution). So, both must be avoided. You also better want to isolate every hudson build from each other, having a local repository by job. And wiping those jobs regularly. http://www.sonatype.com/people/2009/01/maven-continuous-integration-best-practices/ <http://www.sonatype.com/people/2009/01/maven-continuous-integration-best-practices/>And a specific setting for hudson on my blog: http://batmat.net/blog/post/2009/10/09/[Hudson]-How-to-set-a-private-maven-repository-by-job-and-easily-be-able-to-delete-them Cheers" If somebody from here have a different opinion, I'm still interested. Thank you, Em. On Wed, Sep 15, 2010 at 10:23 AM, Em DauPhu <[email protected]> wrote: > Hi, > > I came across a continuous integration server hosting both an Hudson > and an Archiva (as a proxy to our central). The settings.xml used in > maven builds declare as the local repo the managed repository of the > archiva. > Is that wrong to use as a local repository (declared in the maven > settings.xml) the actual managed repository of the archiva proxy? Can > it leads to any trouble ? > > Thank you, > Em. >
