yes, Maestro might be a good alternative to run Continuum and Archiva parallel. However we decided to keep independence and greatest freedom of configuration.
I have discovered that the issue is caused by Continuum, not by Archiva. Continuum has a two phase build-process, which is an undocumented feature AFAIK. This feature easily turns out like a bug. See my post in continuum mailing-list. -----Ursprüngliche Nachricht----- Von: Michael Mallete [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 30. April 2008 09:20 An: [email protected] Betreff: Re: Archiva scanning the standard Mvn repo by default? Not exactly an answer, but have you looked into the Maestro distribution which bundles all three projects (Maven, Continuum, Archiva) http://www.exist.com/?q=node/150 Would spare you all the configuration and integration stuff. Except I don't think what's bundled is the latest versions of each project. On Tue, Apr 29, 2008 at 4:22 PM, Lustig, Marc (Allianz Deutschland AG) < [EMAIL PROTECTED]> wrote: > > We have Continuum and Archiva running on the same server. > The local mvn repo is in the default location (~/.m2) > The Archiva repos are in different places (internal and snapshot). > We are running a build on Continuum "install" that creates a snapshot > and installs it to the local Maven-repo. > > Strangely, those SNAPSHOT's appear after two hours in the local Archiva > snapshot repository, and with a different id. Does Archiva by default > scan the standard Maven-repo (which is not explicitly configured in > Archiva? > >
