Maven 3.1.1
Hervé, You finish looking at everything you wanted to for 3.1.1? Thanks, Jason -- Jason van Zyl 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
Re: Release Maven 3.1.1
I'm push out the MRR release vote tomorrow morning if no one else gets to it. On Aug 9, 2013, at 7:35 PM, Jason van Zyl wrote: > Not planning on it this weekend, if you want to go ahead. > > On Aug 9, 2013, at 2:45 PM, Dennis Lundberg wrote: > >> Hi Jason, >> >> Are you going to start the release vote for the Remote Resource Plugin? >> >> On Mon, Jul 29, 2013 at 3:37 PM, Jason van Zyl wrote: >>> Tag deleted, repository dropped, and now re-released and restaged. >>> >>> https://repository.apache.org/content/repositories/maven-034/ >>> >>> On Jul 29, 2013, at 9:22 AM, Dennis Lundberg wrote: >>> Yes, the loss of Maven 2.2.1 compatibility is critical IMO. On Mon, Jul 29, 2013 at 3:10 PM, Jason van Zyl wrote: > Is this critical for this release? I staged the release already? > > On Jul 29, 2013, at 5:39 AM, Dennis Lundberg wrote: > >> Hi Jason >> >> I had a fix for MRRESOURCES-61 that I have committed to trunk now. >> >> When testing out the sample project that is in that issue I first had >> problems running it with maven-remote-resources-plugin 1.5-SNAPSHOT on >> Maven 2.2.1. After adding a missing dependency I got it working again. >> It works fine with 1.4 though, so for that reason I think we need to >> respin the release for maven-remote-resources-plugin. If you want to I >> can take care of it. >> >> >> The error I got was this: >> >> this realm = >> app0.child-container[org.apache.maven.plugins:maven-remote-resources-plugin:1.5-SNAPSHOT] >> urls[0] = >> file:/C:/Users/dlg01/.m2/repository/org/apache/maven/plugins/maven-remote-resources-plugin/1.5-SNAPSHOT/maven-remote-resources-plugin-1.5-SNAPSHOT.jar >> urls[1] = >> file:/C:/Users/dlg01/.m2/repository/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar >> ... >> >> [INFO] Internal error in the plugin manager executing goal >> 'org.apache.maven.plugins:maven-remote-resources-plugin:1.5-SNAPSHOT:process': >> Unable to load the mojo >> 'org.apache.maven.plugins:maven-remote-resources-plugin:1.5-SNAPSHOT:process' >> in the plugin 'org.apache.maven.plugins:maven-remote-resources-plugin'. >> A required class is missing: org/codehaus/plexus/util/Scanner >> >> The Scanner class wasn't added to plexus-utils until version 1.5.8, so >> using the default version 1.1 won't work. >> >> >> On Mon, Jul 29, 2013 at 1:04 AM, Jason van Zyl wrote: >>> I staged a release of the remote resources plugin for anyone who wants >>> to try: >>> >>> https://repository.apache.org/content/repositories/maven-030/ >>> >>> How about we do a simultaneous release vote for the core and the remote >>> resources plugin? >>> >>> On Jul 28, 2013, at 3:56 PM, Dennis Lundberg wrote: >>> Hi, There is currently a SNAPSHOT dependency on maven-remote-resources-plugin. This was done in this commit by Daniel to improve the LICENCE file: https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=b4dc8931f2cc7b56302df78c03a7db57211cd3a7 The question is whether we need to push out a release of that plugin prior to releasing Maven 3.1.1? I just made a small commit, adding a missing license header in a test xml file. Since I don't speak git very well yet, could someone make sure I did it correctly? https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=a58b91819c42c0a5a8616dc5562ba42287fa0f24 On Sun, Jul 28, 2013 at 6:08 PM, Jason van Zyl wrote: > I'd like to release Maven 3.1.1 and try to get the cadence revived > for minor version releases by trying to release minor versions as > frequently as there are fixes to make available. > > Just a couple simple fixes: > > [MNG-5499] maven-aether-provider leaks Sisu Plexus and ObjectWeb > classes onto the classpath when they are not required > [MNG-5495] API incompatibility causes Swagger Maven Plugin (and > others) to fail under Maven 3.1.0 > > But helps consumers of the Maven Aether Provider and plugin issues > caused by incompatibilities with the converters. There are lots of > other things to fix, but as they become available they can be > released. If possible I'd just like to start releasing any fixes we > have on a weekly basis. > > Any objections? > > Thanks, > > Jason > > -- > Jason van Zyl > Founder, Apache Maven > http://twitter.com/jvanzyl > - > > A man enjoys his work when
Re: [VOTE] Release Apache Maven Mapping version 1.0
+1 On 11 August 2013 09:09, Dennis Lundberg wrote: > Hi, > > This is a new shared component consisting of code from Maven WAR > Plugin, that has been repackaged for reuse by other plugins. > > We solved 1 issues: > http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761&styleName=Html&version=19526 > > There no issues left in JIRA: > http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11761&component=16150&status=1 > > Staging repo: > https://repository.apache.org/content/repositories/maven-083/ > https://repository.apache.org/content/repositories/maven-083/org/apache/maven/shared/maven-mapping/1.0/maven-mapping-1.0-source-release.zip > > Staging site: > http://maven.apache.org/shared-archives/maven-mapping-1.0/ > > Guide to testing staged releases: > http://maven.apache.org/guides/development/guide-testing-releases.html > > Vote open for 72 hours. > > [ ] +1 > [ ] +0 > [ ] -1 > > -- > Dennis Lundberg > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven Model Converter version 2.3
On 12 August 2013 20:10, Jason van Zyl wrote: > >>> >>> I have now read the threads that are referring to, and have not found >>> a single link to any ASF rule stating that we need to include these >>> things in a VOTE thread. >> >> So how do you propose that reviewers check the provenance of the files >> in the source release? > > Are you looking for files that are in a distribution that didn't come from > source control? Everything else as far as provenance goes is covered. Errant > content is a potential problem, but everything in a distribution should come > from source control which no one has access to until they have a signed CLA > on file. Yes. That is where the whole saga started. Proving provenance is why the SCM coordinates are needed for the vote. The SCM details may also be useful to discover files accidentally omitted from the source archive. > Thanks, > > Jason > > -- > Jason van Zyl > Founder, Apache Maven > http://twitter.com/jvanzyl > - > > > > > > > - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven Model Converter version 2.3
>> >> I have now read the threads that are referring to, and have not found >> a single link to any ASF rule stating that we need to include these >> things in a VOTE thread. > > So how do you propose that reviewers check the provenance of the files > in the source release? Are you looking for files that are in a distribution that didn't come from source control? Everything else as far as provenance goes is covered. Errant content is a potential problem, but everything in a distribution should come from source control which no one has access to until they have a signed CLA on file. Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl -
Re: [VOTE] Release Apache Maven Model Converter version 2.3
On 11 August 2013 15:02, Dennis Lundberg wrote: > On Thu, Jul 25, 2013 at 8:03 PM, Dennis Lundberg > wrote: >> On Thu, Jul 25, 2013 at 7:15 PM, sebb wrote: >>> On 25 July 2013 17:50, Dennis Lundberg wrote: On Thu, Jul 25, 2013 at 6:34 PM, sebb wrote: > On 25 July 2013 16:55, Dennis Lundberg wrote: >> Den 25 jul 2013 16:08 skrev "sebb" : >>> >>> On 23 July 2013 20:45, Dennis Lundberg wrote: >>> > Hi, >>> > >>> > This will be the final release of this shared component. After this >>> > release it will retire from the Apache Maven project and move to the >>> > Apache Archiva project. See separate vote thread about that. >>> > >>> > We solved 6 issues: >>> > >> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761&styleName=Html&version=14389 >>> > >>> > There are no issues left in JIRA (except for the one to retire, which >>> > I'll close later): >>> > >> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11761&component=13272&status=1 >>> > >>> > Staging repo: >>> > https://repository.apache.org/content/repositories/maven-010/ >>> > >> https://repository.apache.org/content/repositories/maven-010/org/apache/maven/shared/maven-model-converter/2.3/maven-model-converter-2.3-source-release.zip >>> > >>> > Staging site (not synced yet): >>> > http://maven.apache.org/shared-archives/maven-model-converter-2.3/ >>> > >>> > Guide to testing staged releases: >>> > http://maven.apache.org/guides/development/guide-testing-releases.html >>> >>> What are the unique SCM coordinates? >> >> The SCM URL can be found in the pom file at the staging repo. > > As already mentioned in another thread, the staging repo URL is > temporary (and in fact can be reused for something completely > different). > > Nor does it uniquely identify the code in SCM, as the revision is missing. > > So it is not suitable for documenting the SCM coordinates. In the normal case, where a release is approved on the first round, there is only ever one tag in SVN and it will not be changed. In these cases I do not see the value of including the revision number at all. If a release fails on the first attempt, we reuse the tag. This means that the tag will exist at multiple revisions. If you are an archealogist and find out the revision number of an ancient vote, you can look at the date/time of the vote mail and compare that to the revision dates in SVN. Still I do not see the value of this. The last tag standing is the one that got approved. >>> >>> Provided that the tag is not accidentally or deliberately changed >>> subsequently. >> >> It is not. That is how we work. The only time we ever manually touch a >> tag is when we respin a release. >> Is there an ASF requirement to include the SCM revision number in a release vote? I can't find one. >>> >>> This was all discussed at great length already; please see my other >>> postings on the subject. >> >> I'm sorry, but I'm drowning in email at the moment, and have not read >> up on all threads. >> A simple yes or no answer will suffice for the moment. > > I have now read the threads that are referring to, and have not found > a single link to any ASF rule stating that we need to include these > things in a VOTE thread. So how do you propose that reviewers check the provenance of the files in the source release? > >> -- >> Dennis Lundberg >> >>> >>> > Vote open for 72 hours. >>> > >>> > [ ] +1 >>> > [ ] +0 >>> > [ ] -1 >>> > >>> > -- >>> > Dennis Lundberg >>> > >>> > - >>> > 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 > -- Dennis Lundberg - 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 >>> >> >> >> >> -- >> Dennis Lundberg > > > > -- > Dennis Lundberg > > --
