I'm not totally sure, but I think this sentence refers to the structure (groupId(dots replaced with subdirs)/artifactId/version), not compulsorily the attached metadata. I just checked on my box and on our internal archiva instance, for example, maven-metadata.xml on the server is renamed locally maven-metadata-[repositoryId].xml. Sure, repository manager like nexus or archiva are able to recreate re-index those directories, but I think it might be complicated for it to also handle the potentially highly concurrent access aspect of the problem (hudson jobs + deployment: in your case reading a file locally, and writing to this very file after having gone through the http stack or so while deploying :-/).
Cheers 2010/9/15 Em DauPhu <emdau...@gmail.com> > Didn't know metadata were different, as I quoted from maven website: > "the local and remote repositories are structured the same way". > > Thank you for the great answer, couldn't expect less from an ig2k student > ;) > Ig2k forever :-). > Em. > > On Wed, Sep 15, 2010 at 11:16 AM, Baptiste MATHUS <m...@batmat.net> wrote: > > Hi, > > > > 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 > > > > 2010/9/15 Em DauPhu <emdau...@gmail.com> > > > >> 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 (same directory). > >> Is that wrong to use as a local repository (declared in the maven > >> settings.xml) the actual managed repository of the repository manager? > >> Can it leads to any trouble (it apparently does)? > >> > >> I'm about to change that anyway but I could use some explanations as > >> "the local and remote repositories are structured the same way" if it > >> causes any trouble. > >> > >> Thank you, > >> Em. > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > >> For additional commands, e-mail: users-h...@maven.apache.org > >> > >> > > > > > > -- > > Baptiste <Batmat> MATHUS - http://batmat.net > > Sauvez un arbre, > > Mangez un castor ! > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > -- Baptiste <Batmat> MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
