On 28 August 2012 08:02, Kristian Rosenvold <[email protected]>wrote:
> We're switching topic somewhat, but who cares: > > For Surefire I am still left with the problem that repository<->local > repo directory operations are not safe for > multiple concurrent processes, which seems to affect an mrm-based > solution. This may very quickly apply to core IT's too, since I > considered making them parallel ;) (~15 minutes is drag) > > IIRC mrm will block the other processes from downloading the same artifact, so each forked maven will be stalled until the artifact is fully downloaded into the parent local repo, after which they will all be copying the exact same full artifact into place... > I whacked together a few bits of pieces of code that scans all the IT > projects and installs all the artifacts to the local repository before > running the IT's in parallel forks. Suppose I could add that target > somewhere invoker-like (or mrm). > invoker might make sense... in any case mrm's natural home is invoker too > > > Kristian > > 2012/8/28 Stephen Connolly <[email protected]>: > > I wonder should we pull mrm-maven-plugin into apache and use that instead > > > > On 28 August 2012 02:11, Brian Fox <[email protected]> wrote: > > > >> There are lots of tests that are trying to use file based repositories > >> for certain conditions. This is why in 2.0.9 I had added the > >> external:* : > >> > >> external:* matches all repositories except those using localhost or > >> file based repositories. This is used in conjunction with a repository > >> manager when you want to exclude redirecting repositories that are > >> defined for Integration Testing. > >> > >> Maybe we should update the default setting.xml in the book, but it's > >> pretty rare that people are using file repos for their ITs (read: > >> pretty much only maven ;-) ) > >> > >> On Thu, Aug 23, 2012 at 2:44 PM, Kristian Rosenvold > >> <[email protected]> wrote: > >> > When I try to run the maven core IT's with a mirrorOf setting in my > >> > settings.xml (copy-paste from > >> > > >> > http://www.sonatype.com/books/nexus-book/reference/maven-sect-single-group.html > >> ) > >> > I get all sorts of > >> > weird & wonderful artifact resolution failures for snapshots inside > >> > the forked test processes; this happens regardless of which maven 3.x > >> > version I try to test. > >> > > >> > Removing the the setup from settings.xml clearly fixes the problem. > >> > Can someone explain what is going on, is this a jira issue or WTF ? > >> > > >> > Kristian > >> > > >> > --------------------------------------------------------------------- > >> > 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] > >
