Re: Why do the core its fail massively when using mirrorOf in settings.xml ?
I wonder should we pull mrm-maven-plugin into apache and use that instead On 28 August 2012 02:11, Brian Fox bri...@infinity.nu 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 kristian.rosenv...@gmail.com 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: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Why do the core its fail massively when using mirrorOf in settings.xml ?
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) 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). Kristian 2012/8/28 Stephen Connolly stephen.alan.conno...@gmail.com: I wonder should we pull mrm-maven-plugin into apache and use that instead On 28 August 2012 02:11, Brian Fox bri...@infinity.nu 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 kristian.rosenv...@gmail.com 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: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Why do the core its fail massively when using mirrorOf in settings.xml ?
On 28 August 2012 08:02, Kristian Rosenvold kristian.rosenv...@gmail.comwrote: 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 stephen.alan.conno...@gmail.com: I wonder should we pull mrm-maven-plugin into apache and use that instead On 28 August 2012 02:11, Brian Fox bri...@infinity.nu 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 kristian.rosenv...@gmail.com 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: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Why do the core its fail massively when using mirrorOf in settings.xml ?
Thanks a lot ;) There is no end to how much time someone (=me) can waste on this. I will update the docs on the core IT's about this; since I actually did try reading the manual ;) /me wonders If I can read that setting and basically make the Core IT's refuse to run with it enabled...? Kristian 2012/8/28 Brian Fox bri...@infinity.nu: 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 kristian.rosenv...@gmail.com 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: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Why do the core its fail massively when using mirrorOf in settings.xml ?
I will document this in the Nexus book. Should be available with the next release of it.. manfred On Tue, August 28, 2012 2:37 am, Kristian Rosenvold wrote: Thanks a lot ;) There is no end to how much time someone (=me) can waste on this. I will update the docs on the core IT's about this; since I actually did try reading the manual ;) /me wonders If I can read that setting and basically make the Core IT's refuse to run with it enabled...? Kristian 2012/8/28 Brian Fox bri...@infinity.nu: 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 kristian.rosenv...@gmail.com 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: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Why do the core its fail massively when using mirrorOf in settings.xml ?
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 kristian.rosenv...@gmail.com 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: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Why do the core its fail massively when using mirrorOf in settings.xml ?
I definitely use external:* I didn't even notice the book doesn't. On Aug 27, 2012, at 9:11 PM, Brian Fox 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 kristian.rosenv...@gmail.com 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: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder CTO, Sonatype Founder, Apache Maven http://twitter.com/jvanzyl - First, the taking in of scattered particulars under one Idea, so that everyone understands what is being talked about ... Second, the separation of the Idea into parts, by dividing it at the joints, as nature directs, not breaking any limb in half as a bad carver might. -- Plato, Phaedrus (Notes on the Synthesis of Form by C. Alexander)
Why do the core its fail massively when using mirrorOf in settings.xml ?
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: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Why do the core its fail massively when using mirrorOf in settings.xml ?
I haven't run them in a couple weeks so maybe something has changed recently for local setups, but I have the ITs running in Hudson against Nexus and locally I always use Nexus. In both cases without issue using a mirrorOf setting. I'll try again tonight and see if it's something that recently cropped up, but never had a problem with this. On Aug 23, 2012, at 2:44 PM, Kristian Rosenvold 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: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder CTO, Sonatype Founder, Apache Maven http://twitter.com/jvanzyl - Our achievements speak for themselves. What we have to keep track of are our failures, discouragements and doubts. We tend to forget the past difficulties, the many false starts, and the painful groping. We see our past achievements as the end result of a clean forward thrust, and our present difficulties as signs of decline and decay. -- Eric Hoffer, Reflections on the Human Condition
