Re: [VOTE] Release Maven 3.1.1

2013-09-09 Thread sebb
On 9 September 2013 20:56, Stephen Connolly wrote: > On 8 September 2013 18:51, Jason van Zyl wrote: > >> >> On Sep 8, 2013, at 1:12 PM, sebb wrote: >> >> > I thought you were going to include the SCM coordinates used to create >> > the tarballs? >> > >> >> Sorry, not intentional. I forgot. >> >

RE: Failure to find artifact in Nexus

2013-09-09 Thread John Dix
https://jira.codehaus.org/browse/MNG-5181 ... The use of the MAVEN_OPTS flag has resolved this issue for us. However now it is telling us that maven-clean-plugin 2.5 cannot be found in our release repository. This might be an ancillary issue as we have not encountered this before until I used th

Re: [VOTE] Release Maven 3.1.1

2013-09-09 Thread Stephen Connolly
On 8 September 2013 18:51, Jason van Zyl wrote: > > On Sep 8, 2013, at 1:12 PM, sebb wrote: > > > I thought you were going to include the SCM coordinates used to create > > the tarballs? > > > > Sorry, not intentional. I forgot. > > > It's particularly important here, because AFAICT the SCM coor

Re: [VOTE] Release Maven 3.1.1

2013-09-09 Thread Mark Derricutt
+1 (non-binding) - tested releases against our OSGi based setup using maven-bundle-plugin, my own coffeescript mojos and others. Nothing glaringly out of order for me. -- Mark Derricutt — twitter — podcast — blog — google+ On 9/09/2013, at 1:07 AM, Jason van Zyl wrote: > Here is a link to Jir

[RESULT] [VOTE] Release Apache Maven Install Plugin version 2.5

2013-09-09 Thread Robert Scholte
Hi, The vote has passed with the following result: +1 (binding): Robert Scholte, Olivier Lamy, Hervé BOUTEMY +1 (non binding): I will promote the artifacts to the central repo. thanks, Robert Op Mon, 09 Sep 2013 19:47:09 +0200 schreef Hervé BOUTEMY : +1 Regards, Hervé Le vendredi 6 se

Re: [VOTE] Release Maven 3.1.1

2013-09-09 Thread Jason van Zyl
Awesome, thanks. On Sep 9, 2013, at 3:19 PM, Mirko Friedenhagen wrote: > +1 (non-binding), tested with extra-enforcer-rules, testlink-junit and > jenkinsci-jobConfigHistory-plugin. > Regards Mirko > -- > http://illegalstateexception.blogspot.com/ > https://github.com/mfriedenhagen/ > https://bit

Re: [VOTE] Release Maven 3.1.1

2013-09-09 Thread Mirko Friedenhagen
+1 (non-binding), tested with extra-enforcer-rules, testlink-junit and jenkinsci-jobConfigHistory-plugin. Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ https://bitbucket.org/mfriedenhagen/ On Sun, Sep 8, 2013 at 3:07 PM, Jason van Zyl wrote: > Hi,

RE: Failure to find artifact in Nexus

2013-09-09 Thread John Dix
Still repro's in Maven 3.1. The bug says it is fixed there if I am reading it correctly. However, the artifact is stored in Nexus in exactly where we want it: 3rdparty. Maven pulls it down, and rather than acknowledge it's existence in the local .m2 repository, it continues to try and find it an

Re: maven-scm-provider-jgit

2013-09-09 Thread domi
Olivier and all, sorry, I'm not really a member of the maven dev team - so I wanted to ask what the options could be to make some progress on this or if you feel that the jgit scm-provider should rather be hosted somewhere else then @ASF? So far it looks like the tests just fail on one single ins

Re: Failure to find artifact in Nexus

2013-09-09 Thread Laird Nelson
On Mon, Sep 9, 2013 at 10:29 AM, John Dix wrote: > Still repro's in Maven 3.1. The bug says it is fixed there if I am reading > it correctly. However, the artifact is stored in Nexus in exactly where we > want it: 3rdparty. Maven pulls it down, and rather than acknowledge it's > existence in the

RE: Failure to find artifact in Nexus

2013-09-09 Thread John Dix
I am deleting the .m2/repository (rm -rf ~/.m2/repository/*) before every build. I have used the -U before as well. -Original Message- From: Robert Scholte [mailto:rfscho...@apache.org] Sent: Monday, September 09, 2013 10:41 AM To: Maven Developers List Subject: Re: Failure to find artifa

Re: [VOTE] Release Apache Maven Install Plugin version 2.5

2013-09-09 Thread Hervé BOUTEMY
+1 Regards, Hervé Le vendredi 6 septembre 2013 21:35:56 Robert Scholte a écrit : > Hi, > > We solved 6 issues: > http://jira.codehaus.org/secure/ReleaseNote.jspa?styleName=Html&projectId=11 > 136&version=18760 > > There are still a couple of issues left in JIRA: > http://jira.codehaus.org/secu

Re: Failure to find artifact in Nexus

2013-09-09 Thread Robert Scholte
Well, it is actually not a bug, but a more strict behavior of Maven 3 compared to Maven 2. The issue is a solution to get the Maven 2 behavior with Maven 3. In short: Maven 3 tries to predict if the project can still be built with an empty repository, even if the dependencies are available in

RE: Failure to find artifact in Nexus

2013-09-09 Thread John Dix
Thanks! The problem is not that I am not getting the artifact because I am. The problem is that Maven acts like it doesn't have the file(after downloading it) and then exits. If I rerun the build it passes just fine. It does this on very specific artifacts every time. It is very reproducible. W

Re: Failure to find artifact in Nexus

2013-09-09 Thread Robert Scholte
In that case you're probably hitting https://jira.codehaus.org/browse/MNG-5181 Robert Op Mon, 09 Sep 2013 18:57:25 +0200 schreef John Dix : What I mean by being "downloaded" is that it is easily found in the local .m2 repository of the machine maven is being executed on. -Original Mes

RE: Failure to find artifact in Nexus

2013-09-09 Thread John Dix
What I mean by being "downloaded" is that it is easily found in the local .m2 repository of the machine maven is being executed on. -Original Message- From: John Dix Sent: Monday, September 09, 2013 9:44 AM To: Maven Developers List Subject: RE: Failure to find artifact in Nexus Thanks!