Re: [VOTE] Apache 3.1.0-alpha-1 (Take 4)
Another late +1 from me. Looks good. I'm on vacation this week in Florida but found some time last night to run it against a handful of projects and didn't run into any issues. :) Wayne On Sat, Jun 1, 2013 at 8:13 AM, Jason van Zyl ja...@tesla.io wrote: Here are the release bits for 3.1.0-alpha-1: Release notes: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=18967 Staging repository: https://repository.apache.org/content/repositories/maven-046/ Staged distribution: https://repository.apache.org/content/repositories/maven-046/org/apache/maven/apache-maven/3.1.0-alpha-1/ Staged Site: http://maven.apache.org/ref/3.1.0-alpha-1 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)
Re: [VOTE] Apache 3.1.0-alpha-1 (Take 4)
+1 2013/6/1 Jason van Zyl ja...@tesla.io: Here are the release bits for 3.1.0-alpha-1: Release notes: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=18967 Staging repository: https://repository.apache.org/content/repositories/maven-046/ Staged distribution: https://repository.apache.org/content/repositories/maven-046/org/apache/maven/apache-maven/3.1.0-alpha-1/ Staged Site: http://maven.apache.org/ref/3.1.0-alpha-1 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) -- 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] Apache 3.1.0-alpha-1 (Take 4)
+1 On Sat, Jun 1, 2013 at 9:13 AM, Jason van Zyl ja...@tesla.io wrote: Here are the release bits for 3.1.0-alpha-1: Release notes: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=18967 Staging repository: https://repository.apache.org/content/repositories/maven-046/ Staged distribution: https://repository.apache.org/content/repositories/maven-046/org/apache/maven/apache-maven/3.1.0-alpha-1/ Staged Site: http://maven.apache.org/ref/3.1.0-alpha-1 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) - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Apache 3.1.0-alpha-1 (Take 4)
+1: Arnaud, Hervé, Brian, Baptiste, Mirko Vote passes. I will roll out the release later today. On Jun 4, 2013, at 12:13 PM, Brian Fox bri...@infinity.nu wrote: +1 On Sat, Jun 1, 2013 at 9:13 AM, Jason van Zyl ja...@tesla.io wrote: Here are the release bits for 3.1.0-alpha-1: Release notes: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=18967 Staging repository: https://repository.apache.org/content/repositories/maven-046/ Staged distribution: https://repository.apache.org/content/repositories/maven-046/org/apache/maven/apache-maven/3.1.0-alpha-1/ Staged Site: http://maven.apache.org/ref/3.1.0-alpha-1 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) - 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 - Script timed out
Re: [VOTE] Apache 3.1.0-alpha-1 (Take 4)
+1 (binding) On 1 June 2013 14:13, Jason van Zyl ja...@tesla.io wrote: Here are the release bits for 3.1.0-alpha-1: Release notes: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=18967 Staging repository: https://repository.apache.org/content/repositories/maven-046/ Staged distribution: https://repository.apache.org/content/repositories/maven-046/org/apache/maven/apache-maven/3.1.0-alpha-1/ Staged Site: http://maven.apache.org/ref/3.1.0-alpha-1 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)
Re: [VOTE] Apache 3.1.0-alpha-1 (Take 4)
Awesome! Congrats to everyone involved. I am looking forward to adapting the Android Maven Plugin and releasing a new version asap! Manfred +1: Arnaud, Hervé, Brian, Baptiste, Mirko Vote passes. I will roll out the release later today. On Jun 4, 2013, at 12:13 PM, Brian Fox bri...@infinity.nu wrote: +1 On Sat, Jun 1, 2013 at 9:13 AM, Jason van Zyl ja...@tesla.io wrote: Here are the release bits for 3.1.0-alpha-1: Release notes: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=18967 Staging repository: https://repository.apache.org/content/repositories/maven-046/ Staged distribution: https://repository.apache.org/content/repositories/maven-046/org/apache/maven/apache-maven/3.1.0-alpha-1/ Staged Site: http://maven.apache.org/ref/3.1.0-alpha-1 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) - 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 - Script timed out - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Apache 3.1.0-alpha-1 (Take 4)
W00t - congrats to the Apache Maven Team Now... about that Maven 4.0 release... ;p Manfred Moser wrote: Awesome! Congrats to everyone involved. I am looking forward to adapting the Android Maven Plugin and releasing a new version asap! Manfred +1: Arnaud, Hervé, Brian, Baptiste, Mirko Vote passes. I will roll out the release later today. On Jun 4, 2013, at 12:13 PM, Brian Foxbri...@infinity.nu wrote: +1 On Sat, Jun 1, 2013 at 9:13 AM, Jason van Zylja...@tesla.io wrote: Here are the release bits for 3.1.0-alpha-1: Release notes: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=18967 Staging repository: https://repository.apache.org/content/repositories/maven-046/ Staged distribution: https://repository.apache.org/content/repositories/maven-046/org/apache/maven/apache-maven/3.1.0-alpha-1/ Staged Site: http://maven.apache.org/ref/3.1.0-alpha-1 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) - 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 - Script timed out - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Apache 3.1.0-alpha-1 (Take 4)
+1 did run it the last 2 days on many of my projects without any issues. LieGrue, strub - Original Message - From: Brian Fox bri...@infinity.nu To: Maven Developers List dev@maven.apache.org Cc: Sent: Tuesday, 4 June 2013, 18:13 Subject: Re: [VOTE] Apache 3.1.0-alpha-1 (Take 4) +1 On Sat, Jun 1, 2013 at 9:13 AM, Jason van Zyl ja...@tesla.io wrote: Here are the release bits for 3.1.0-alpha-1: Release notes: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=18967 Staging repository: https://repository.apache.org/content/repositories/maven-046/ Staged distribution: https://repository.apache.org/content/repositories/maven-046/org/apache/maven/apache-maven/3.1.0-alpha-1/ Staged Site: http://maven.apache.org/ref/3.1.0-alpha-1 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) - 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: [VOTE] Apache 3.1.0-alpha-1 (Take 4)
+1 Regards, Hervé Le samedi 1 juin 2013 09:13:17 Jason van Zyl a écrit : Here are the release bits for 3.1.0-alpha-1: Release notes: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=18 967 Staging repository: https://repository.apache.org/content/repositories/maven-046/ Staged distribution: https://repository.apache.org/content/repositories/maven-046/org/apache/mave n/apache-maven/3.1.0-alpha-1/ Staged Site: http://maven.apache.org/ref/3.1.0-alpha-1 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) - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Apache 3.1.0-alpha-1 (Take 4)
+1 Le dimanche 2 juin 2013, Hervé BOUTEMY a écrit : +1 Regards, Hervé Le samedi 1 juin 2013 09:13:17 Jason van Zyl a écrit : Here are the release bits for 3.1.0-alpha-1: Release notes: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=18 967 Staging repository: https://repository.apache.org/content/repositories/maven-046/ Staged distribution: https://repository.apache.org/content/repositories/maven-046/org/apache/mave n/apache-maven/3.1.0-alpha-1/ Staged Site: http://maven.apache.org/ref/3.1.0-alpha-1 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) - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org javascript:; For additional commands, e-mail: dev-h...@maven.apache.org javascript:; -- - Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier
Re: [VOTE] Apache 3.1.0-alpha-1 (Take 4)
+1. 2013/6/2 Arnaud Héritier aherit...@gmail.com +1 Le dimanche 2 juin 2013, Hervé BOUTEMY a écrit : +1 Regards, Hervé Le samedi 1 juin 2013 09:13:17 Jason van Zyl a écrit : Here are the release bits for 3.1.0-alpha-1: Release notes: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=18 967 Staging repository: https://repository.apache.org/content/repositories/maven-046/ Staged distribution: https://repository.apache.org/content/repositories/maven-046/org/apache/mave n/apache-maven/3.1.0-alpha-1/ Staged Site: http://maven.apache.org/ref/3.1.0-alpha-1 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) - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org javascript:; For additional commands, e-mail: dev-h...@maven.apache.orgjavascript:; -- - Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
Re: [VOTE] Apache 3.1.0-alpha-1
ok, the auto installer ant_maven.groovy script gets every released Maven version from our official release area [1] Then *any released* version will be available: once Maven 3.1.0-alpha-1 will be released, it will be shown by this script, ready to have many eyes, even if this release is only alpha Isn't it sufficient? Did you really think at making staged versions auto-installable, during the vote period, before the release? Regards, Hervé [1] http://archive.apache.org/dist/maven/binaries/ Le vendredi 31 mai 2013 07:01:19 jieryn a écrit : Greetings, On Fri, May 31, 2013 at 1:34 AM, Hervé BOUTEMY herve.bout...@free.fr wrote: I don't know what you mean by send pull requests to Jenkins, if you're talking about Apache's Jenkins instance or something more general from the Jenkins project There is something called the backend-crawler which locates common tools that can be auto-installed by the Jenkins service itself. All Jenkins instances will load a JSON file, similar to the way it knows which plugins can be auto-installed. I meant we should perhaps send a pull request here: https://github.com/jenkinsci/backend-crawler/blob/master/ant_maven.groovy More information here: https://wiki.jenkins-ci.org/display/JENKINS/Adding+tool+auto-installer https://wiki.jenkins-ci.org/display/JENKINS/Tool+Auto-Installation but I'm interested by the it would be auto-installable objective at least on Apache's Jenkins instance Yep, that or someone with karma can just manually install it and enable it as the default builder? That way it won't break any builds which require a specific Apache Maven. But the auto-installable route would enable more places to just quickly enable it.. I'm not sure if Jenkins folks would be receptive to having an Apache Maven pre-release kind of thing showing up in their tool list, but off the top of my head I can not find a reasonable objection. -Jesse - 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: [VOTE] Apache 3.1.0-alpha-1 (Take 4)
+1 (non-binding) for (c726cdd3a9ad5c3a419e1171f8c1925e336ead18): - I successfully ran mvn verify site for some of my own projects (pom-only, one jar, multi-module). - the current trunk of maven-javadoc-plugin encountered some failing ITs. [ERROR] * additionnal-dependencies-non-aggregate/pom.xml [ERROR] * additionnal-dependencies/pom.xml [ERROR] * MJAVADOC-257/pom.xml [ERROR] * MJAVADOC-259/pom.xml [ERROR] * MJAVADOC-369/pom.xml [ERROR] * site-failOnError/pom.xml all of which failed because of the move of aether(https://jira.codehaus.org/browse/MNG-5354): Caused by: org.apache.maven.plugin.PluginExecutionException: Execution default-site of goal org.apache.maven.plugins:maven-site-plugin:3.1:site failed: A required class was missing while executing org.apache.maven.plugins:maven-site-plugin:3.1:site: org/sonatype/aether/graph/DependencyFilter More complete error at http://pastebin.com/fVP26axg In my local copy of the extra-enforcer-rules after setting the version of maven-site-plugin to 3.3, I was able to build the site successfully. So please put a big warning that projects have to update some plugins when updating to 3.1.0 :-) Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ https://bitbucket.org/mfriedenhagen/ On Sat, Jun 1, 2013 at 3:13 PM, Jason van Zyl ja...@tesla.io wrote: Here are the release bits for 3.1.0-alpha-1: Release notes: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=18967 Staging repository: https://repository.apache.org/content/repositories/maven-046/ Staged distribution: https://repository.apache.org/content/repositories/maven-046/org/apache/maven/apache-maven/3.1.0-alpha-1/ Staged Site: http://maven.apache.org/ref/3.1.0-alpha-1 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) - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Apache 3.1.0-alpha-1
Greetings, On Fri, May 31, 2013 at 1:34 AM, Hervé BOUTEMY herve.bout...@free.fr wrote: I don't know what you mean by send pull requests to Jenkins, if you're talking about Apache's Jenkins instance or something more general from the Jenkins project There is something called the backend-crawler which locates common tools that can be auto-installed by the Jenkins service itself. All Jenkins instances will load a JSON file, similar to the way it knows which plugins can be auto-installed. I meant we should perhaps send a pull request here: https://github.com/jenkinsci/backend-crawler/blob/master/ant_maven.groovy More information here: https://wiki.jenkins-ci.org/display/JENKINS/Adding+tool+auto-installer https://wiki.jenkins-ci.org/display/JENKINS/Tool+Auto-Installation but I'm interested by the it would be auto-installable objective at least on Apache's Jenkins instance Yep, that or someone with karma can just manually install it and enable it as the default builder? That way it won't break any builds which require a specific Apache Maven. But the auto-installable route would enable more places to just quickly enable it.. I'm not sure if Jenkins folks would be receptive to having an Apache Maven pre-release kind of thing showing up in their tool list, but off the top of my head I can not find a reasonable objection. -Jesse - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Apache 3.1.0-alpha-1
On 31 May 2013 12:01, jieryn jie...@gmail.com wrote: Greetings, On Fri, May 31, 2013 at 1:34 AM, Hervé BOUTEMY herve.bout...@free.fr wrote: I don't know what you mean by send pull requests to Jenkins, if you're talking about Apache's Jenkins instance or something more general from the Jenkins project There is something called the backend-crawler which locates common tools that can be auto-installed by the Jenkins service itself. All Jenkins instances will load a JSON file, similar to the way it knows which plugins can be auto-installed. I meant we should perhaps send a pull request here: https://github.com/jenkinsci/backend-crawler/blob/master/ant_maven.groovy More information here: https://wiki.jenkins-ci.org/display/JENKINS/Adding+tool+auto-installer https://wiki.jenkins-ci.org/display/JENKINS/Tool+Auto-Installation but I'm interested by the it would be auto-installable objective at least on Apache's Jenkins instance Yep, that or someone with karma can just manually install it and enable it as the default builder? That way it won't break any builds which require a specific Apache Maven. But the auto-installable route would enable more places to just quickly enable it.. I'm not sure if Jenkins folks would be receptive to having an Apache Maven pre-release kind of thing showing up in their tool list, but off the top of my head I can not find a reasonable objection. Wearing my Jenkins hat, I would not be happy with pre-release bits showing up unless they had a clear (pre-release) tag, and I don't think there is an easy way to uninstall tools from the build slaves... But I think it would be a good topic to bring up at the next Jenkins Board meeting (not that I ever attend those due to TZ issues) Note: Given KKs view of how bad an idea reusing version numbers is, I suspect that KK would be against the pre-release as long as we allow respinning with the same version number... but there is no harm in asking the question -Stephen -Jesse - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Apache 3.1.0-alpha-1
If one was to push this out for Jenkins to pick them - then this puts a cobwash on the other thread of reusing version numbers IMHO.If you're going to let alpha-1 bleed out to the greater internet, IT IS RELEASED :)IMHO. --Mark DerricuttSent with AirmailOn 31 May 2013 at 11:18:52 PM, Stephen Connolly (stephen.alan.conno...@gmail.com) wrote: Wearing my Jenkins hat, I would not be happy with pre-release bits showingup unless they had a clear (pre-release) tag, and I don't think there is aneasy way to uninstall tools from the build slaves... - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Apache 3.1.0-alpha-1
Perfect. Thx On Thu, May 30, 2013 at 3:27 AM, Hervé BOUTEMY herve.bout...@free.frwrote: MNG-5482 fixed: ok for me to go for take 4 when a plugin cannot be loaded due to missing Sonatype Aether class, hint url will be http://cwiki.apache.org/confluence/display/MAVEN/AetherClassNotFound the Wiki article still needs to be written... Regards, Hervé Le mercredi 29 mai 2013 09:34:46 Arnaud Héritier a écrit : On Wed, May 29, 2013 at 7:39 AM, Hervé BOUTEMY herve.bout...@free.fr wrote: good idea: can you open a Jira issue? Done : https://jira.codehaus.org/browse/MNG-5482 Another probably more stupid idea : Wasn't it possible to use the shade plugin or something like this to provide a version of aether under the old groupId to not have such requirement in plugins upgrades ? Something that we'll have been able to remove in a next major release (4) Good news, about Aether I perhaps found an improvement in its performances : https://gist.github.com/aheritier/5668330 It's interesting for me but won't be so impressive for 99,99% of projects where the dependency resolution time is really reduced compared to others tasks (compilation, tests ..) Bad news I also found a bug : https://jira.codehaus.org/browse/MNG-5483 Cheers, notice, at a first pass, improving content of http://cwiki.apache.org/confluence/display/MAVEN/PluginContainerExceptiont o explain the special case of Aether is easy. But I'll try to have a dedicated link tonight: I know that the code will go in DefaultExceptionHandler class in maven-core, my only hesitation actually is how to code ITs to test the result: are there already ITs checking such error messages? Regards, Hervé Le mardi 28 mai 2013 18:31:26 Arnaud Héritier a écrit : For now I had no issue with this release after an upgrade of few plugins In the future (another Alpha ..) couldn't you catch such error and provide a more user friendly message asking to upgrade the plugin : [INFO] Dependency-reduced POM written at: /Users/arnaud/Code/eXo/platform-public-distributions/plf-tomcat-extensions -m anager/dependency-reduced-pom.xml [WARNING] Error injecting: org.apache.maven.shared.dependency.graph.internal.Maven3DependencyGraphBui ld er java.lang.NoClassDefFoundError: org/sonatype/aether/graph/Dependency at java.lang.Class.getDeclaredMethods0(Native Method) at java.lang.Class.privateGetDeclaredMethods(Class.java:2436) at java.lang.Class.getDeclaredMethods(Class.java:1793) at com.google.inject.spi.InjectionPoint.getInjectionPoints(InjectionPoint.java: 674) at com.google.inject.spi.InjectionPoint.forInstanceMethodsAndFields(Injection Po int.java:366) at com.google.inject.internal.ConstructorBindingImpl.getInternalDependencies( Co nstructorBindingImpl.java:165) at com.google.inject.internal.InjectorImpl.getInternalDependencies(InjectorIm pl .java:609) at com.google.inject.internal.InjectorImpl.cleanup(InjectorImpl.java:565) at com.google.inject.internal.InjectorImpl.initializeJitBinding(InjectorImpl. ja va:551) at com.google.inject.internal.InjectorImpl.createJustInTimeBinding(InjectorIm pl .java:865) at com.google.inject.internal.InjectorImpl.createJustInTimeBindingRecursive(I nj ectorImpl.java:790) at com.google.inject.internal.InjectorImpl.getJustInTimeBinding(InjectorImpl. ja va:278) at com.google.inject.internal.InjectorImpl.getBindingOrThrow(InjectorImpl.java: 210) at com.google.inject.internal.InjectorImpl.getProviderOrThrow(InjectorImpl.ja va :986) at com.google.inject.internal.InjectorImpl.getProvider(InjectorImpl.java:1019 ) at com.google.inject.internal.InjectorImpl.getProvider(InjectorImpl.java:982) at com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:1032 ) at org.eclipse.sisu.reflect.AbstractDeferredClass.get(AbstractDeferredClass.j av a:44) at com.google.inject.internal.ProviderInternalFactory.provision(ProviderInter na lFactory.java:86) at com.google.inject.internal.InternalFactoryToInitializableAdapter.provision (I nternalFactoryToInitializableAdapter.java:55) at com.google.inject.internal.ProviderInternalFactory$1.call(ProviderInternal Fa ctory.java:70) at com.google.inject.internal.ProvisionListenerStackCallback$Provision.provis io n(ProvisionListenerStackCallback.java:100) at org.eclipse.sisu.plexus.lifecycles.PlexusLifecycleManager.onProvision(Plex us LifecycleManager.java:134) at com.google.inject.internal.ProvisionListenerStackCallback$Provision.provis io n(ProvisionListenerStackCallback.java:109) at
Re: [VOTE] Apache 3.1.0-alpha-1
https://cwiki.apache.org/confluence/display/MAVEN/AetherClassNotFound page created improvements welcome Regards, Hervé Le jeudi 30 mai 2013 09:10:50 Arnaud Héritier a écrit : Perfect. Thx On Thu, May 30, 2013 at 3:27 AM, Hervé BOUTEMY herve.bout...@free.frwrote: MNG-5482 fixed: ok for me to go for take 4 when a plugin cannot be loaded due to missing Sonatype Aether class, hint url will be http://cwiki.apache.org/confluence/display/MAVEN/AetherClassNotFound the Wiki article still needs to be written... Regards, Hervé Le mercredi 29 mai 2013 09:34:46 Arnaud Héritier a écrit : On Wed, May 29, 2013 at 7:39 AM, Hervé BOUTEMY herve.bout...@free.fr wrote: good idea: can you open a Jira issue? Done : https://jira.codehaus.org/browse/MNG-5482 Another probably more stupid idea : Wasn't it possible to use the shade plugin or something like this to provide a version of aether under the old groupId to not have such requirement in plugins upgrades ? Something that we'll have been able to remove in a next major release (4) Good news, about Aether I perhaps found an improvement in its performances : https://gist.github.com/aheritier/5668330 It's interesting for me but won't be so impressive for 99,99% of projects where the dependency resolution time is really reduced compared to others tasks (compilation, tests ..) Bad news I also found a bug : https://jira.codehaus.org/browse/MNG-5483 Cheers, notice, at a first pass, improving content of http://cwiki.apache.org/confluence/display/MAVEN/PluginContainerExceptiont o explain the special case of Aether is easy. But I'll try to have a dedicated link tonight: I know that the code will go in DefaultExceptionHandler class in maven-core, my only hesitation actually is how to code ITs to test the result: are there already ITs checking such error messages? Regards, Hervé Le mardi 28 mai 2013 18:31:26 Arnaud Héritier a écrit : For now I had no issue with this release after an upgrade of few plugins In the future (another Alpha ..) couldn't you catch such error and provide a more user friendly message asking to upgrade the plugin : [INFO] Dependency-reduced POM written at: /Users/arnaud/Code/eXo/platform-public-distributions/plf-tomcat-extensions -m anager/dependency-reduced-pom.xml [WARNING] Error injecting: org.apache.maven.shared.dependency.graph.internal.Maven3DependencyGraphBui ld er java.lang.NoClassDefFoundError: org/sonatype/aether/graph/Dependency at java.lang.Class.getDeclaredMethods0(Native Method) at java.lang.Class.privateGetDeclaredMethods(Class.java:2436) at java.lang.Class.getDeclaredMethods(Class.java:1793) at com.google.inject.spi.InjectionPoint.getInjectionPoints(InjectionPoint.java: 674) at com.google.inject.spi.InjectionPoint.forInstanceMethodsAndFields(Injection Po int.java:366) at com.google.inject.internal.ConstructorBindingImpl.getInternalDependencies( Co nstructorBindingImpl.java:165) at com.google.inject.internal.InjectorImpl.getInternalDependencies(InjectorIm pl .java:609) at com.google.inject.internal.InjectorImpl.cleanup(InjectorImpl.java:565) at com.google.inject.internal.InjectorImpl.initializeJitBinding(InjectorImpl. ja va:551) at com.google.inject.internal.InjectorImpl.createJustInTimeBinding(InjectorIm pl .java:865) at com.google.inject.internal.InjectorImpl.createJustInTimeBindingRecursive(I nj ectorImpl.java:790) at com.google.inject.internal.InjectorImpl.getJustInTimeBinding(InjectorImpl. ja va:278) at com.google.inject.internal.InjectorImpl.getBindingOrThrow(InjectorImpl.java: 210) at com.google.inject.internal.InjectorImpl.getProviderOrThrow(InjectorImpl.ja va :986) at com.google.inject.internal.InjectorImpl.getProvider(InjectorImpl.java:1019 ) at com.google.inject.internal.InjectorImpl.getProvider(InjectorImpl.java:982) at com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:1032 ) at org.eclipse.sisu.reflect.AbstractDeferredClass.get(AbstractDeferredClass.j av a:44) at com.google.inject.internal.ProviderInternalFactory.provision(ProviderInter na lFactory.java:86) at com.google.inject.internal.InternalFactoryToInitializableAdapter.provision (I nternalFactoryToInitializableAdapter.java:55) at com.google.inject.internal.ProviderInternalFactory$1.call(ProviderInternal Fa ctory.java:70) at
Re: [VOTE] Apache 3.1.0-alpha-1
Ok, we're just waiting now for Stephen to summarize the vote and then when we figure out what to call it I'll roll out the release. On May 30, 2013, at 2:32 PM, Hervé BOUTEMY herve.bout...@free.fr wrote: https://cwiki.apache.org/confluence/display/MAVEN/AetherClassNotFound page created improvements welcome Regards, Hervé Le jeudi 30 mai 2013 09:10:50 Arnaud Héritier a écrit : Perfect. Thx On Thu, May 30, 2013 at 3:27 AM, Hervé BOUTEMY herve.bout...@free.frwrote: MNG-5482 fixed: ok for me to go for take 4 when a plugin cannot be loaded due to missing Sonatype Aether class, hint url will be http://cwiki.apache.org/confluence/display/MAVEN/AetherClassNotFound the Wiki article still needs to be written... Regards, Hervé Le mercredi 29 mai 2013 09:34:46 Arnaud Héritier a écrit : On Wed, May 29, 2013 at 7:39 AM, Hervé BOUTEMY herve.bout...@free.fr wrote: good idea: can you open a Jira issue? Done : https://jira.codehaus.org/browse/MNG-5482 Another probably more stupid idea : Wasn't it possible to use the shade plugin or something like this to provide a version of aether under the old groupId to not have such requirement in plugins upgrades ? Something that we'll have been able to remove in a next major release (4) Good news, about Aether I perhaps found an improvement in its performances : https://gist.github.com/aheritier/5668330 It's interesting for me but won't be so impressive for 99,99% of projects where the dependency resolution time is really reduced compared to others tasks (compilation, tests ..) Bad news I also found a bug : https://jira.codehaus.org/browse/MNG-5483 Cheers, notice, at a first pass, improving content of http://cwiki.apache.org/confluence/display/MAVEN/PluginContainerExceptiont o explain the special case of Aether is easy. But I'll try to have a dedicated link tonight: I know that the code will go in DefaultExceptionHandler class in maven-core, my only hesitation actually is how to code ITs to test the result: are there already ITs checking such error messages? Regards, Hervé Le mardi 28 mai 2013 18:31:26 Arnaud Héritier a écrit : For now I had no issue with this release after an upgrade of few plugins In the future (another Alpha ..) couldn't you catch such error and provide a more user friendly message asking to upgrade the plugin : [INFO] Dependency-reduced POM written at: /Users/arnaud/Code/eXo/platform-public-distributions/plf-tomcat-extensions -m anager/dependency-reduced-pom.xml [WARNING] Error injecting: org.apache.maven.shared.dependency.graph.internal.Maven3DependencyGraphBui ld er java.lang.NoClassDefFoundError: org/sonatype/aether/graph/Dependency at java.lang.Class.getDeclaredMethods0(Native Method) at java.lang.Class.privateGetDeclaredMethods(Class.java:2436) at java.lang.Class.getDeclaredMethods(Class.java:1793) at com.google.inject.spi.InjectionPoint.getInjectionPoints(InjectionPoint.java: 674) at com.google.inject.spi.InjectionPoint.forInstanceMethodsAndFields(Injection Po int.java:366) at com.google.inject.internal.ConstructorBindingImpl.getInternalDependencies( Co nstructorBindingImpl.java:165) at com.google.inject.internal.InjectorImpl.getInternalDependencies(InjectorIm pl .java:609) at com.google.inject.internal.InjectorImpl.cleanup(InjectorImpl.java:565) at com.google.inject.internal.InjectorImpl.initializeJitBinding(InjectorImpl. ja va:551) at com.google.inject.internal.InjectorImpl.createJustInTimeBinding(InjectorIm pl .java:865) at com.google.inject.internal.InjectorImpl.createJustInTimeBindingRecursive(I nj ectorImpl.java:790) at com.google.inject.internal.InjectorImpl.getJustInTimeBinding(InjectorImpl. ja va:278) at com.google.inject.internal.InjectorImpl.getBindingOrThrow(InjectorImpl.java: 210) at com.google.inject.internal.InjectorImpl.getProviderOrThrow(InjectorImpl.ja va :986) at com.google.inject.internal.InjectorImpl.getProvider(InjectorImpl.java:1019 ) at com.google.inject.internal.InjectorImpl.getProvider(InjectorImpl.java:982) at com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:1032 ) at org.eclipse.sisu.reflect.AbstractDeferredClass.get(AbstractDeferredClass.j av a:44) at com.google.inject.internal.ProviderInternalFactory.provision(ProviderInter na lFactory.java:86) at com.google.inject.internal.InternalFactoryToInitializableAdapter.provision (I nternalFactoryToInitializableAdapter.java:55) at com.google.inject.internal.ProviderInternalFactory$1.call(ProviderInternal Fa ctory.java:70) at com.google.inject.internal.ProvisionListenerStackCallback$Provision.provis io n(ProvisionListenerStackCallback.java:100) at org.eclipse.sisu.plexus.lifecycles.PlexusLifecycleManager.onProvision(Plex us LifecycleManager.java:134) at
Re: [VOTE] Apache 3.1.0-alpha-1
You are the release manager. My vote on respinning specifically stated that any releases in progress, the release manager can decide. If it were me I'd call it 3.1.0-beta-1 as we have had enough eyes by now that its better than alpha... I'd also be happy going straight for the 3.1.0 end game... But if you want to hold 3.1.0 as a sacred number and fear the respinning vote going +3, then -beta-1 would give you breathing room. TL;DR lets get this bad boy out! On Thursday, 30 May 2013, Jason van Zyl wrote: Ok, we're just waiting now for Stephen to summarize the vote and then when we figure out what to call it I'll roll out the release. On May 30, 2013, at 2:32 PM, Hervé BOUTEMY herve.bout...@free.fr wrote: https://cwiki.apache.org/confluence/display/MAVEN/AetherClassNotFound page created improvements welcome Regards, Hervé Le jeudi 30 mai 2013 09:10:50 Arnaud Héritier a écrit : Perfect. Thx On Thu, May 30, 2013 at 3:27 AM, Hervé BOUTEMY herve.bout...@free.fr wrote: MNG-5482 fixed: ok for me to go for take 4 when a plugin cannot be loaded due to missing Sonatype Aether class, hint url will be http://cwiki.apache.org/confluence/display/MAVEN/AetherClassNotFound the Wiki article still needs to be written... Regards, Hervé Le mercredi 29 mai 2013 09:34:46 Arnaud Héritier a écrit : On Wed, May 29, 2013 at 7:39 AM, Hervé BOUTEMY herve.bout...@free.fr wrote: good idea: can you open a Jira issue? Done : https://jira.codehaus.org/browse/MNG-5482 Another probably more stupid idea : Wasn't it possible to use the shade plugin or something like this to provide a version of aether under the old groupId to not have such requirement in plugins upgrades ? Something that we'll have been able to remove in a next major release (4) Good news, about Aether I perhaps found an improvement in its performances : https://gist.github.com/aheritier/5668330 It's interesting for me but won't be so impressive for 99,99% of projects where the dependency resolution time is really reduced compared to others tasks (compilation, tests ..) Bad news I also found a bug : https://jira.codehaus.org/browse/MNG-5483 Cheers, notice, at a first pass, improving content of http://cwiki.apache.org/confluence/display/MAVEN/PluginContainerExceptiont o explain the special case of Aether is easy. But I'll try to have a dedicated link tonight: I know that the code will go in DefaultExceptionHandler class in maven-core, my only hesitation actually is how to code ITs to test the result: are there already ITs checking such error messages? Regards, Hervé Le mardi 28 mai 2013 18:31:26 Arnaud Héritier a écrit : For now I had no issue with this release after an upgrade of few plugins In the future (another Alpha ..) couldn't you catch such error and provide a more user friendly message asking to upgrade the plugin : [INFO] Dependency-reduced POM written at: /Users/arnaud/Code/eXo/platform-public-distributions/plf-tomcat-extensions -m 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) -- Sent from my phone
Re: [VOTE] Apache 3.1.0-alpha-1
I'm going to stick to alpha-1. No one has looked at it save 10 people which doesn't, to me, constitute any reasonably sized population. I'll roll it out in the morning. On May 30, 2013, at 4:15 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: You are the release manager. My vote on respinning specifically stated that any releases in progress, the release manager can decide. If it were me I'd call it 3.1.0-beta-1 as we have had enough eyes by now that its better than alpha... I'd also be happy going straight for the 3.1.0 end game... But if you want to hold 3.1.0 as a sacred number and fear the respinning vote going +3, then -beta-1 would give you breathing room. TL;DR lets get this bad boy out! On Thursday, 30 May 2013, Jason van Zyl wrote: Ok, we're just waiting now for Stephen to summarize the vote and then when we figure out what to call it I'll roll out the release. On May 30, 2013, at 2:32 PM, Hervé BOUTEMY herve.bout...@free.fr wrote: https://cwiki.apache.org/confluence/display/MAVEN/AetherClassNotFound page created improvements welcome Regards, Hervé Le jeudi 30 mai 2013 09:10:50 Arnaud Héritier a écrit : Perfect. Thx On Thu, May 30, 2013 at 3:27 AM, Hervé BOUTEMY herve.bout...@free.fr wrote: MNG-5482 fixed: ok for me to go for take 4 when a plugin cannot be loaded due to missing Sonatype Aether class, hint url will be http://cwiki.apache.org/confluence/display/MAVEN/AetherClassNotFound the Wiki article still needs to be written... Regards, Hervé Le mercredi 29 mai 2013 09:34:46 Arnaud Héritier a écrit : On Wed, May 29, 2013 at 7:39 AM, Hervé BOUTEMY herve.bout...@free.fr wrote: good idea: can you open a Jira issue? Done : https://jira.codehaus.org/browse/MNG-5482 Another probably more stupid idea : Wasn't it possible to use the shade plugin or something like this to provide a version of aether under the old groupId to not have such requirement in plugins upgrades ? Something that we'll have been able to remove in a next major release (4) Good news, about Aether I perhaps found an improvement in its performances : https://gist.github.com/aheritier/5668330 It's interesting for me but won't be so impressive for 99,99% of projects where the dependency resolution time is really reduced compared to others tasks (compilation, tests ..) Bad news I also found a bug : https://jira.codehaus.org/browse/MNG-5483 Cheers, notice, at a first pass, improving content of http://cwiki.apache.org/confluence/display/MAVEN/PluginContainerExceptiont o explain the special case of Aether is easy. But I'll try to have a dedicated link tonight: I know that the code will go in DefaultExceptionHandler class in maven-core, my only hesitation actually is how to code ITs to test the result: are there already ITs checking such error messages? Regards, Hervé Le mardi 28 mai 2013 18:31:26 Arnaud Héritier a écrit : For now I had no issue with this release after an upgrade of few plugins In the future (another Alpha ..) couldn't you catch such error and provide a more user friendly message asking to upgrade the plugin : [INFO] Dependency-reduced POM written at: /Users/arnaud/Code/eXo/platform-public-distributions/plf-tomcat-extensions -m 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) -- Sent from my phone Thanks, Jason -- Jason van Zyl Founder CTO, Sonatype Founder, Apache Maven http://twitter.com/jvanzyl - To do two things at once is to do neither. -- Publilius Syrus, Roman slave, first century B.C.
Re: [VOTE] Apache 3.1.0-alpha-1
Go for it! (Aside: not sure that we'll get that much more eyes for 3.1.0-alpha-x... I think the eyes will only hit it when we get to 3.1.0...) On Thursday, 30 May 2013, Jason van Zyl wrote: I'm going to stick to alpha-1. No one has looked at it save 10 people which doesn't, to me, constitute any reasonably sized population. I'll roll it out in the morning. On May 30, 2013, at 4:15 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: You are the release manager. My vote on respinning specifically stated that any releases in progress, the release manager can decide. If it were me I'd call it 3.1.0-beta-1 as we have had enough eyes by now that its better than alpha... I'd also be happy going straight for the 3.1.0 end game... But if you want to hold 3.1.0 as a sacred number and fear the respinning vote going +3, then -beta-1 would give you breathing room. TL;DR lets get this bad boy out! On Thursday, 30 May 2013, Jason van Zyl wrote: Ok, we're just waiting now for Stephen to summarize the vote and then when we figure out what to call it I'll roll out the release. On May 30, 2013, at 2:32 PM, Hervé BOUTEMY herve.bout...@free.fr wrote: https://cwiki.apache.org/confluence/display/MAVEN/AetherClassNotFound page created improvements welcome Regards, Hervé Le jeudi 30 mai 2013 09:10:50 Arnaud Héritier a écrit : Perfect. Thx On Thu, May 30, 2013 at 3:27 AM, Hervé BOUTEMY herve.bout...@free.fr wrote: MNG-5482 fixed: ok for me to go for take 4 when a plugin cannot be loaded due to missing Sonatype Aether class, hint url will be http://cwiki.apache.org/confluence/display/MAVEN/AetherClassNotFound the Wiki article still needs to be written... Regards, Hervé Le mercredi 29 mai 2013 09:34:46 Arnaud Héritier a écrit : On Wed, May 29, 2013 at 7:39 AM, Hervé BOUTEMY herve.bout...@free.fr wrote: good idea: can you open a Jira issue? Done : https://jira.codehaus.org/browse/MNG-5482 Another probably more stupid idea : Wasn't it possible to use the shade plugin or something like this to provide a version of aether under the old groupId to not have such requirement in plugins upgrades ? Something that we'll have been able to remove in a next major release (4) Good news, about Aether I perhaps found an improvement in its performances : https://gist.github.com/aheritier/5668330 It's interesting for me but won't be so impressive for 99,99% of projects where the dependency resolution time is really reduced compared to others tasks (compilation, tests ..) Bad news I also found a bug : https://jira.codehaus.org/browse/MNG-5483 Cheers, notice, at a first pass, improving content of http://cwiki.apache.org/confluence/display/MAVEN/PluginContainerExceptiont Thanks, Jason -- Jason van Zyl Founder CTO, Sonatype Founder, Apache Maven http://twitter.com/jvanzyl - To do two things at once is to do neither. -- Publilius Syrus, Roman slave, first century B.C. -- Sent from my phone
Re: [VOTE] Apache 3.1.0-alpha-1
Greetings, On Thu, May 30, 2013 at 4:29 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: (Aside: not sure that we'll get that much more eyes for 3.1.0-alpha-x... I think the eyes will only hit it when we get to 3.1.0...) It would be nice if someone sent pull requests to Jenkins so that it would be auto-installable. I wonder if that would help getting more testing in place. -Jesse - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Apache 3.1.0-alpha-1
I don't know what you mean by send pull requests to Jenkins, if you're talking about Apache's Jenkins instance or something more general from the Jenkins project but I'm interested by the it would be auto-installable objective at least on Apache's Jenkins instance so I'll read any pointer to more precise explanations to see if can do anyhting in this direction Regards, Hervé Le jeudi 30 mai 2013 16:33:58 jieryn a écrit : Greetings, On Thu, May 30, 2013 at 4:29 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: (Aside: not sure that we'll get that much more eyes for 3.1.0-alpha-x... I think the eyes will only hit it when we get to 3.1.0...) It would be nice if someone sent pull requests to Jenkins so that it would be auto-installable. I wonder if that would help getting more testing in place. -Jesse - 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: [VOTE] Apache 3.1.0-alpha-1
On May 29, 2013 7:49 AM, jieryn jie...@gmail.com wrote: Greetings, On Wed, May 29, 2013 at 1:36 AM, Hervé BOUTEMY herve.bout...@free.fr wrote: I'd like to work on Arnaud's idea of error message enhancement in case a plugin fails because of unavailable Sonatype Aether: if you can let me 12 more hours from now, I'll do it tonight Version numbers are cheap. Can't we just make an alpha-2? +1 to Jesse's suggestion. In every other software reusing version numbers is a nono. Regards Mirko
Re: [VOTE] Apache 3.1.0-alpha-1
Le 29 mai 2013 08:07, Mirko Friedenhagen mfriedenha...@gmail.com a écrit : On May 29, 2013 7:49 AM, jieryn jie...@gmail.com wrote: Greetings, On Wed, May 29, 2013 at 1:36 AM, Hervé BOUTEMY herve.bout...@free.fr wrote: I'd like to work on Arnaud's idea of error message enhancement in case a plugin fails because of unavailable Sonatype Aether: if you can let me 12 more hours from now, I'll do it tonight Version numbers are cheap. Can't we just make an alpha-2? +1 to Jesse's suggestion. In every other software reusing version numbers is a nono. Though tempting, I only agree with you for pre-releases (alpha, beta ...). I think this would create more mess for users having non qualified versions in the wild that have actually been garbage from the beginning... average users wont look at pre-release anyway. Cheers
Re: [VOTE] Apache 3.1.0-alpha-1
alpha-1 to n works fine imo. We should not loose pace by holding up the effort with such minor stuff. LieGrue, strub - Original Message - From: Baptiste Mathus bmat...@gmail.com To: Maven Developers List dev@maven.apache.org Cc: Sent: Wednesday, 29 May 2013, 8:47 Subject: Re: [VOTE] Apache 3.1.0-alpha-1 Le 29 mai 2013 08:07, Mirko Friedenhagen mfriedenha...@gmail.com a écrit : On May 29, 2013 7:49 AM, jieryn jie...@gmail.com wrote: Greetings, On Wed, May 29, 2013 at 1:36 AM, Hervé BOUTEMY herve.bout...@free.fr wrote: I'd like to work on Arnaud's idea of error message enhancement in case a plugin fails because of unavailable Sonatype Aether: if you can let me 12 more hours from now, I'll do it tonight Version numbers are cheap. Can't we just make an alpha-2? +1 to Jesse's suggestion. In every other software reusing version numbers is a nono. Though tempting, I only agree with you for pre-releases (alpha, beta ...). I think this would create more mess for users having non qualified versions in the wild that have actually been garbage from the beginning... average users wont look at pre-release anyway. Cheers - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Apache 3.1.0-alpha-1
On Wed, May 29, 2013 at 7:39 AM, Hervé BOUTEMY herve.bout...@free.frwrote: good idea: can you open a Jira issue? Done : https://jira.codehaus.org/browse/MNG-5482 Another probably more stupid idea : Wasn't it possible to use the shade plugin or something like this to provide a version of aether under the old groupId to not have such requirement in plugins upgrades ? Something that we'll have been able to remove in a next major release (4) Good news, about Aether I perhaps found an improvement in its performances : https://gist.github.com/aheritier/5668330 It's interesting for me but won't be so impressive for 99,99% of projects where the dependency resolution time is really reduced compared to others tasks (compilation, tests ..) Bad news I also found a bug : https://jira.codehaus.org/browse/MNG-5483 Cheers, notice, at a first pass, improving content of http://cwiki.apache.org/confluence/display/MAVEN/PluginContainerExceptionto explain the special case of Aether is easy. But I'll try to have a dedicated link tonight: I know that the code will go in DefaultExceptionHandler class in maven-core, my only hesitation actually is how to code ITs to test the result: are there already ITs checking such error messages? Regards, Hervé Le mardi 28 mai 2013 18:31:26 Arnaud Héritier a écrit : For now I had no issue with this release after an upgrade of few plugins In the future (another Alpha ..) couldn't you catch such error and provide a more user friendly message asking to upgrade the plugin : [INFO] Dependency-reduced POM written at: /Users/arnaud/Code/eXo/platform-public-distributions/plf-tomcat-extensions-m anager/dependency-reduced-pom.xml [WARNING] Error injecting: org.apache.maven.shared.dependency.graph.internal.Maven3DependencyGraphBuild er java.lang.NoClassDefFoundError: org/sonatype/aether/graph/Dependency at java.lang.Class.getDeclaredMethods0(Native Method) at java.lang.Class.privateGetDeclaredMethods(Class.java:2436) at java.lang.Class.getDeclaredMethods(Class.java:1793) at com.google.inject.spi.InjectionPoint.getInjectionPoints(InjectionPoint.java: 674) at com.google.inject.spi.InjectionPoint.forInstanceMethodsAndFields(InjectionPo int.java:366) at com.google.inject.internal.ConstructorBindingImpl.getInternalDependencies(Co nstructorBindingImpl.java:165) at com.google.inject.internal.InjectorImpl.getInternalDependencies(InjectorImpl .java:609) at com.google.inject.internal.InjectorImpl.cleanup(InjectorImpl.java:565) at com.google.inject.internal.InjectorImpl.initializeJitBinding(InjectorImpl.ja va:551) at com.google.inject.internal.InjectorImpl.createJustInTimeBinding(InjectorImpl .java:865) at com.google.inject.internal.InjectorImpl.createJustInTimeBindingRecursive(Inj ectorImpl.java:790) at com.google.inject.internal.InjectorImpl.getJustInTimeBinding(InjectorImpl.ja va:278) at com.google.inject.internal.InjectorImpl.getBindingOrThrow(InjectorImpl.java: 210) at com.google.inject.internal.InjectorImpl.getProviderOrThrow(InjectorImpl.java :986) at com.google.inject.internal.InjectorImpl.getProvider(InjectorImpl.java:1019) at com.google.inject.internal.InjectorImpl.getProvider(InjectorImpl.java:982) at com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:1032) at org.eclipse.sisu.reflect.AbstractDeferredClass.get(AbstractDeferredClass.jav a:44) at com.google.inject.internal.ProviderInternalFactory.provision(ProviderInterna lFactory.java:86) at com.google.inject.internal.InternalFactoryToInitializableAdapter.provision(I nternalFactoryToInitializableAdapter.java:55) at com.google.inject.internal.ProviderInternalFactory$1.call(ProviderInternalFa ctory.java:70) at com.google.inject.internal.ProvisionListenerStackCallback$Provision.provisio n(ProvisionListenerStackCallback.java:100) at org.eclipse.sisu.plexus.lifecycles.PlexusLifecycleManager.onProvision(Plexus LifecycleManager.java:134) at com.google.inject.internal.ProvisionListenerStackCallback$Provision.provisio n(ProvisionListenerStackCallback.java:109) at com.google.inject.internal.ProvisionListenerStackCallback.provision(Provisio nListenerStackCallback.java:55) at com.google.inject.internal.ProviderInternalFactory.circularGet(ProviderInter nalFactory.java:68) at com.google.inject.internal.InternalFactoryToInitializableAdapter.get(Interna lFactoryToInitializableAdapter.java:47) at com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderT oInternalFactoryAdapter.java:46) at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1054 ) at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToIn ternalFactoryAdapter.java:40) at com.google.inject.Scopes$1$1.get(Scopes.java:59) at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFact oryToProviderAdapter.java:41) at
Re: [VOTE] Apache 3.1.0-alpha-1
Arnaud Héritier wrote: On Wed, May 29, 2013 at 7:39 AM, Hervé BOUTEMY herve.bout...@free.frwrote: good idea: can you open a Jira issue? Done : https://jira.codehaus.org/browse/MNG-5482 Another probably more stupid idea : Wasn't it possible to use the shade plugin or something like this to provide a version of aether under the old groupId to not have such requirement in plugins upgrades ? Something that we'll have been able to remove in a next major release (4) Weird idea: A ClassLoader that exchanges the package name automatically, along with a fat deprecation warning? - Jörg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Apache 3.1.0-alpha-1
There were method signature changes as well, so its not just a package rename IIRC On 29 May 2013 08:57, Jörg Schaible joerg.schai...@scalaris.com wrote: Arnaud Héritier wrote: On Wed, May 29, 2013 at 7:39 AM, Hervé BOUTEMY herve.bout...@free.frwrote: good idea: can you open a Jira issue? Done : https://jira.codehaus.org/browse/MNG-5482 Another probably more stupid idea : Wasn't it possible to use the shade plugin or something like this to provide a version of aether under the old groupId to not have such requirement in plugins upgrades ? Something that we'll have been able to remove in a next major release (4) Weird idea: A ClassLoader that exchanges the package name automatically, along with a fat deprecation warning? - Jörg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Apache 3.1.0-alpha-1
On Wed, May 29, 2013 at 10:01 AM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: There were method signature changes as well, so its not just a package rename IIRC Ok that explains it I remember there were some threads about it but I didn't read all of them. On 29 May 2013 08:57, Jörg Schaible joerg.schai...@scalaris.com wrote: Arnaud Héritier wrote: On Wed, May 29, 2013 at 7:39 AM, Hervé BOUTEMY herve.bout...@free.frwrote: good idea: can you open a Jira issue? Done : https://jira.codehaus.org/browse/MNG-5482 Another probably more stupid idea : Wasn't it possible to use the shade plugin or something like this to provide a version of aether under the old groupId to not have such requirement in plugins upgrades ? Something that we'll have been able to remove in a next major release (4) Weird idea: A ClassLoader that exchanges the package name automatically, along with a fat deprecation warning? - Jörg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- - Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier
Re: [VOTE] Apache 3.1.0-alpha-1
On 29 May 2013 06:49, jieryn jie...@gmail.com wrote: Greetings, On Wed, May 29, 2013 at 1:36 AM, Hervé BOUTEMY herve.bout...@free.fr wrote: I'd like to work on Arnaud's idea of error message enhancement in case a plugin fails because of unavailable Sonatype Aether: if you can let me 12 more hours from now, I'll do it tonight Version numbers are cheap. Can't we just make an alpha-2? I'm just a user, but I'm getting pretty sick of staged alpha releases being dropped. This happened with 3.0.5 as well. Just release it already. They are alphas. Christ. Well for the NOTICE.txt issue, we cannot actually make a release for legal reasons without https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commitdiff;h=b0a83f62 being part of the release. The question is whether it is better to have the first 3.1.0 alpha release be called 3.1.0-alpha-4 or 3.1.0-alpha-1 When people come back and look at the git history, they will see the commits with [maven-release] Prepare 3.1.0-alpha-1 through to [maven-release] Prepare 3.1.0-alpha-4 but only see the tag for maven-3.1.0-alpha-4 and they might incorrectly assume that somebody just forgot to push the tag (similarly they could undelete the SVN tag, so this is not a GIT thing) and then you could end up with a situation where the ASF is sued for making a release of Maven without attributing the Eclipse foundation correctly... Yes, I know that specific example is unlikely, but the point is that there is potential for that type of thing... and we have the mailing lists as a record, etc. Jenkins 1.453's borked partial release was enough to convince me that dropping the staging repo and respining with the same version number is probably the lesser evil though that might be because I had to go and do some workarounds for some automated analysis and other fancy shit I was doing. I guess my point is that 3 months later I had to go digging and it took quite some time to find out that Jenkins 1.453 was actually a failed partial release and while there were artifacts for jenkins-core published, there were none for jenkins-war. Prior to 1.453 I would have been agreeing with KK's assertion that the ASF version reuse was just madness. But having said all that, if we can find a good way to flag versions as not released (e.g. a release history page or something) I am not against skipping version numbers. Might confuse people though if that meant that the first release of Maven 3.1.0 was 3.1.4 (i.e. if we had not been doing alpha's) -Jesse - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Apache 3.1.0-alpha-1
2013/5/29 Stephen Connolly stephen.alan.conno...@gmail.com: On 29 May 2013 06:49, jieryn jie...@gmail.com wrote: Greetings, On Wed, May 29, 2013 at 1:36 AM, Hervé BOUTEMY herve.bout...@free.fr wrote: I'd like to work on Arnaud's idea of error message enhancement in case a plugin fails because of unavailable Sonatype Aether: if you can let me 12 more hours from now, I'll do it tonight Version numbers are cheap. Can't we just make an alpha-2? I'm just a user, but I'm getting pretty sick of staged alpha releases being dropped. This happened with 3.0.5 as well. Just release it already. They are alphas. Christ. Well for the NOTICE.txt issue, we cannot actually make a release for legal reasons without https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commitdiff;h=b0a83f62 being part of the release. The question is whether it is better to have the first 3.1.0 alpha release be called 3.1.0-alpha-4 or 3.1.0-alpha-1 When people come back and look at the git history, they will see the commits with [maven-release] Prepare 3.1.0-alpha-1 through to [maven-release] Prepare 3.1.0-alpha-4 but only see the tag for maven-3.1.0-alpha-4 and they might incorrectly assume that somebody just forgot to push the tag (similarly they could undelete the SVN tag, so this is not a GIT thing) and then you could end up with a situation where the ASF is sued for making a release of Maven without attributing the Eclipse foundation correctly... Yes, I know that specific example is unlikely, but the point is that there is potential for that type of thing... and we have the mailing lists as a record, etc. Jenkins 1.453's borked partial release was enough to convince me that dropping the staging repo and respining with the same version number is probably the lesser evil though that might be because I had to go and do some workarounds for some automated analysis and other fancy shit I was doing. I guess my point is that 3 months later I had to go digging and it took quite some time to find out that Jenkins 1.453 was actually a failed partial release and while there were artifacts for jenkins-core published, there were none for jenkins-war. Prior to 1.453 I would have been agreeing with KK's assertion that the ASF version reuse was just madness. But having said all that, if we can find a good way to flag versions as not released (e.g. a release history page or something) I am not against skipping version numbers. Might confuse people though if that meant that the first release of Maven 3.1.0 was 3.1.4 (i.e. if we had not been doing alpha's) it's just consuming a tag for nothing and not having an official Apache release for this tag (not publishing sources or binaries) Where is the issue ? some projects like httpd or tomcat do that. -Jesse - 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] Apache 3.1.0-alpha-1
But having said all that, if we can find a good way to flag versions as not released (e.g. a release history page or something) I am not against skipping version numbers. Might confuse people though if that meant that the first release of Maven 3.1.0 was 3.1.4 (i.e. if we had not been doing alpha's) It is what Tomcat is doing ? They release regularly and depending of feedback they announce it or not AFAIR http://tomcat.apache.org/tomcat-7.0-doc/changelog.html In the changelog (ex 7.0.38) you have a not released instead of the date when they dropped it Arnaud
Re: [VOTE] Apache 3.1.0-alpha-1
Isn't the main source of confusion here that the vote thread is not detached from the previous thread and that Take X is not added to the subject ? Kristian - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Apache 3.1.0-alpha-1
I am fine with it if there is a clear page which shows the status of each release (i.e. linked from the downloads page: http://maven.apache.org/download.cgi) And if we want to go that way, I say let's just drop all the alpha crap. and go for 3.1.0 straight. My point is that there is a trade off... and as such there is no right or wrong answer... only shades of grey On 29 May 2013 09:17, Arnaud Héritier aherit...@gmail.com wrote: But having said all that, if we can find a good way to flag versions as not released (e.g. a release history page or something) I am not against skipping version numbers. Might confuse people though if that meant that the first release of Maven 3.1.0 was 3.1.4 (i.e. if we had not been doing alpha's) It is what Tomcat is doing ? They release regularly and depending of feedback they announce it or not AFAIR http://tomcat.apache.org/tomcat-7.0-doc/changelog.html In the changelog (ex 7.0.38) you have a not released instead of the date when they dropped it Arnaud
Re: [VOTE] Apache 3.1.0-alpha-1
Yup tomcat does it. compare http://archive.apache.org/dist/tomcat/tomcat-7/ with http://svn.apache.org/repos/asf/tomcat/tc7.0.x/tags/ and http://archive.apache.org/dist/tomcat/tomcat-6/ with http://svn.apache.org/repos/asf/tomcat/tc6.0.x/tags/ 2013/5/29 Kristian Rosenvold kristian.rosenv...@gmail.com: Isn't the main source of confusion here that the vote thread is not detached from the previous thread and that Take X is not added to the subject ? Kristian - 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] Apache 3.1.0-alpha-1
Sure, go for it. The less confusing to users the better. On May 29, 2013, at 1:36 AM, Hervé BOUTEMY herve.bout...@free.fr wrote: I'd like to work on Arnaud's idea of error message enhancement in case a plugin fails because of unavailable Sonatype Aether: if you can let me 12 more hours from now, I'll do it tonight Regards, Hervé Le mardi 28 mai 2013 19:21:52 Jason van Zyl a écrit : I'll see if Robert wants to fix the DOAP file and I'll respin tomorrow after he's commented. On May 28, 2013, at 7:17 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: Yep looks fine to me. If you want to respin now, from _my_ PoV *should* be no issues now... of course who knows what will crop up with the next review ;-) On 29 May 2013 00:07, Jason van Zyl ja...@tesla.io wrote: This should suffice for the notice: https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commitdiff;h=b0a83f 62 On May 28, 2013, at 5:48 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: From my PoV the only outstanding issue is that the NOTICE.txt does not reflect the fact that it is now Eclipse Aether and no longer Sonatype Aether. I am unclear what the exact wording that is required, I am hoping that somebody else can correct the file. All the license header issues are, to my mind, fixed on master and Robert has switched over to package-info.java. I'll let Robert comment as to whether he sees the DOAP as a blocker. On 28 May 2013 22:08, Jason van Zyl ja...@tesla.io wrote: It's very easy to cut another release. If all the fixes are in that the PMC wishes it takes minutes to roll the release again. On May 28, 2013, at 4:43 PM, Robert Scholte rfscho...@apache.org wrote: Some additional remarks: - The copyright doesn't include current year (I've already fixed that on the trunk) - doap:generate fails: The generated DOAP doesn't respect ASF rules. Just to be sure I understand correctly: these alpha-versions will never be released. They are created so users can try them. -1 votes would mean it is not yet ready for a beta or final release. Is this right? Robert Op Tue, 28 May 2013 10:38:07 +0200 schreef Stephen Connolly stephen.alan.conno...@gmail.com: [x] Builds from source bundle [x] Builds some complex projects [x] Contains correct LICENSE.txt [ ] NOTICE.txt correctly attributes 3rd party components (See observation 1) [?] All source files, where appropriate, contain the ASL header (See observation 2) [?] Binary archives bundled within the source distribution (See observation 3) On the basis of the NOTICE.txt not acknowledging Eclipse Aether, and only on that basis I will be voting -0.9 (binding) The other issues are non-critical but it would be nice to tidy them up... nice to have. Observations 1. No attribution of Eclipse Aether, only referenced as developed by Sonatype. 2. The following 39 files are missing license headers: apache-maven/src/bin/m2.conf apache-maven/src/conf/logging/simplelogger.properties maven-aether-provider/src/main/java/org/apache/maven/repository/internal/ package.html maven-aether-provider/src/site/apt/index.apt maven-artifact/src/site/apt/index.apt maven-compat/compatibility.cfl maven-compat/src/main/resources/META-INF/maven/plugin.xml maven-core/lifecycle-executor.txt maven-core/plugin-manager.txt maven-core/project-builder.txt maven-core/src/main/resources/org/apache/maven/messages/build.propertie s maven-core/src/site/apt/artifact-handlers.apt maven-core/src/site/apt/configuration-management.apt maven-core/src/site/apt/default-bindings.apt.vm maven-core/src/site/apt/getting-to-container-configured-mojos.apt maven-core/src/site/apt/index.apt maven-core/src/site/apt/inheritance.apt maven-core/src/site/apt/lifecycles.apt.vm maven-core/src/site/apt/offline-mode.apt maven-core/src/site/apt/plugin-execution-isolation.apt maven-core/src/site/apt/scripting-support/marmalade-support.apt maven-core/src/site/resources/design/2.1-lifecycle-refactor.graffle maven-embedder/src/examples/simple-project/src/main/java/org/apache/maven /embedder/App.java maven-embedder/src/examples/simple-project/src/test/java/org/apache/maven /embedder/AppTest.java maven-embedder/src/main/resources/META-INF/MANIFEST.MF maven-embedder/src/main/resources/META-INF/maven/slf4j-configuration.prop erties maven-embedder/src/site/apt/cli.apt.vm maven-embedder/src/site/apt/index.apt.vm maven-embedder/src/site/apt/logging.apt maven-model-builder/src/site/apt/index.apt maven-model-builder/src/site/apt/super-pom.apt.vm maven-model/src/main/java/org/apache/maven/model/io/xpp3/package.html maven-model/src/main/java/org/apache/maven/model/merge/package.html maven-model/src/main/java/org/apache/maven/model/package.html maven-model/src/site/apt/index.apt maven-plugin-api/src/site/apt/index.apt
Re: [VOTE] Apache 3.1.0-alpha-1
DOAP issues have been fixed. Let's wait for Hervé before spinning a new release. Robert Op Wed, 29 May 2013 01:21:52 +0200 schreef Jason van Zyl ja...@tesla.io: I'll see if Robert wants to fix the DOAP file and I'll respin tomorrow after he's commented. On May 28, 2013, at 7:17 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: Yep looks fine to me. If you want to respin now, from _my_ PoV *should* be no issues now... of course who knows what will crop up with the next review ;-) On 29 May 2013 00:07, Jason van Zyl ja...@tesla.io wrote: This should suffice for the notice: https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commitdiff;h=b0a83f62 On May 28, 2013, at 5:48 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: From my PoV the only outstanding issue is that the NOTICE.txt does not reflect the fact that it is now Eclipse Aether and no longer Sonatype Aether. I am unclear what the exact wording that is required, I am hoping that somebody else can correct the file. All the license header issues are, to my mind, fixed on master and Robert has switched over to package-info.java. I'll let Robert comment as to whether he sees the DOAP as a blocker. On 28 May 2013 22:08, Jason van Zyl ja...@tesla.io wrote: It's very easy to cut another release. If all the fixes are in that the PMC wishes it takes minutes to roll the release again. On May 28, 2013, at 4:43 PM, Robert Scholte rfscho...@apache.org wrote: Some additional remarks: - The copyright doesn't include current year (I've already fixed that on the trunk) - doap:generate fails: The generated DOAP doesn't respect ASF rules. Just to be sure I understand correctly: these alpha-versions will never be released. They are created so users can try them. -1 votes would mean it is not yet ready for a beta or final release. Is this right? Robert Op Tue, 28 May 2013 10:38:07 +0200 schreef Stephen Connolly stephen.alan.conno...@gmail.com: [x] Builds from source bundle [x] Builds some complex projects [x] Contains correct LICENSE.txt [ ] NOTICE.txt correctly attributes 3rd party components (See observation 1) [?] All source files, where appropriate, contain the ASL header (See observation 2) [?] Binary archives bundled within the source distribution (See observation 3) On the basis of the NOTICE.txt not acknowledging Eclipse Aether, and only on that basis I will be voting -0.9 (binding) The other issues are non-critical but it would be nice to tidy them up... nice to have. Observations 1. No attribution of Eclipse Aether, only referenced as developed by Sonatype. 2. The following 39 files are missing license headers: apache-maven/src/bin/m2.conf apache-maven/src/conf/logging/simplelogger.properties maven-aether-provider/src/main/java/org/apache/maven/repository/internal/package.html maven-aether-provider/src/site/apt/index.apt maven-artifact/src/site/apt/index.apt maven-compat/compatibility.cfl maven-compat/src/main/resources/META-INF/maven/plugin.xml maven-core/lifecycle-executor.txt maven-core/plugin-manager.txt maven-core/project-builder.txt maven-core/src/main/resources/org/apache/maven/messages/build.properties maven-core/src/site/apt/artifact-handlers.apt maven-core/src/site/apt/configuration-management.apt maven-core/src/site/apt/default-bindings.apt.vm maven-core/src/site/apt/getting-to-container-configured-mojos.apt maven-core/src/site/apt/index.apt maven-core/src/site/apt/inheritance.apt maven-core/src/site/apt/lifecycles.apt.vm maven-core/src/site/apt/offline-mode.apt maven-core/src/site/apt/plugin-execution-isolation.apt maven-core/src/site/apt/scripting-support/marmalade-support.apt maven-core/src/site/resources/design/2.1-lifecycle-refactor.graffle maven-embedder/src/examples/simple-project/src/main/java/org/apache/maven/embedder/App.java maven-embedder/src/examples/simple-project/src/test/java/org/apache/maven/embedder/AppTest.java maven-embedder/src/main/resources/META-INF/MANIFEST.MF maven-embedder/src/main/resources/META-INF/maven/slf4j-configuration.properties maven-embedder/src/site/apt/cli.apt.vm maven-embedder/src/site/apt/index.apt.vm maven-embedder/src/site/apt/logging.apt maven-model-builder/src/site/apt/index.apt maven-model-builder/src/site/apt/super-pom.apt.vm maven-model/src/main/java/org/apache/maven/model/io/xpp3/package.html maven-model/src/main/java/org/apache/maven/model/merge/package.html maven-model/src/main/java/org/apache/maven/model/package.html maven-model/src/site/apt/index.apt maven-plugin-api/src/site/apt/index.apt maven-repository-metadata/src/site/apt/index.apt maven-settings/src/site/apt/index.apt README.bootstrap.txt None of these are actual production code, so I don't see this as a blocker for release, but it would be good to tidy them up. Additionally, the embedder examples should have their license explicitly stated to remove confusion for anyone pegging the examples to
Re: [VOTE] Apache 3.1.0-alpha-1
On Wed, May 29, 2013 at 10:17 AM, Arnaud Héritier aherit...@gmail.com wrote: But having said all that, if we can find a good way to flag versions as not released (e.g. a release history page or something) I am not against skipping version numbers. Might confuse people though if that meant that the first release of Maven 3.1.0 was 3.1.4 (i.e. if we had not been doing alpha's) It is what Tomcat is doing ? They release regularly and depending of feedback they announce it or not AFAIR http://tomcat.apache.org/tomcat-7.0-doc/changelog.html In the changelog (ex 7.0.38) you have a not released instead of the date when they dropped it Well I would like this better. Why not let the non-released tags in git or rename the tag to maven-3.1.0-alpha-1-not-for-public-consumption and just state in the release description of JIRA (https://jira.codehaus.org/browse/MNG#selectedTab=com.atlassian.jira.plugin.system.project%3Aversions-panel) that alpha-1 was never released to the public but only staged for testing. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Apache 3.1.0-alpha-1
MNG-5482 fixed: ok for me to go for take 4 when a plugin cannot be loaded due to missing Sonatype Aether class, hint url will be http://cwiki.apache.org/confluence/display/MAVEN/AetherClassNotFound the Wiki article still needs to be written... Regards, Hervé Le mercredi 29 mai 2013 09:34:46 Arnaud Héritier a écrit : On Wed, May 29, 2013 at 7:39 AM, Hervé BOUTEMY herve.bout...@free.frwrote: good idea: can you open a Jira issue? Done : https://jira.codehaus.org/browse/MNG-5482 Another probably more stupid idea : Wasn't it possible to use the shade plugin or something like this to provide a version of aether under the old groupId to not have such requirement in plugins upgrades ? Something that we'll have been able to remove in a next major release (4) Good news, about Aether I perhaps found an improvement in its performances : https://gist.github.com/aheritier/5668330 It's interesting for me but won't be so impressive for 99,99% of projects where the dependency resolution time is really reduced compared to others tasks (compilation, tests ..) Bad news I also found a bug : https://jira.codehaus.org/browse/MNG-5483 Cheers, notice, at a first pass, improving content of http://cwiki.apache.org/confluence/display/MAVEN/PluginContainerExceptiont o explain the special case of Aether is easy. But I'll try to have a dedicated link tonight: I know that the code will go in DefaultExceptionHandler class in maven-core, my only hesitation actually is how to code ITs to test the result: are there already ITs checking such error messages? Regards, Hervé Le mardi 28 mai 2013 18:31:26 Arnaud Héritier a écrit : For now I had no issue with this release after an upgrade of few plugins In the future (another Alpha ..) couldn't you catch such error and provide a more user friendly message asking to upgrade the plugin : [INFO] Dependency-reduced POM written at: /Users/arnaud/Code/eXo/platform-public-distributions/plf-tomcat-extensions -m anager/dependency-reduced-pom.xml [WARNING] Error injecting: org.apache.maven.shared.dependency.graph.internal.Maven3DependencyGraphBui ld er java.lang.NoClassDefFoundError: org/sonatype/aether/graph/Dependency at java.lang.Class.getDeclaredMethods0(Native Method) at java.lang.Class.privateGetDeclaredMethods(Class.java:2436) at java.lang.Class.getDeclaredMethods(Class.java:1793) at com.google.inject.spi.InjectionPoint.getInjectionPoints(InjectionPoint.java: 674) at com.google.inject.spi.InjectionPoint.forInstanceMethodsAndFields(Injection Po int.java:366) at com.google.inject.internal.ConstructorBindingImpl.getInternalDependencies( Co nstructorBindingImpl.java:165) at com.google.inject.internal.InjectorImpl.getInternalDependencies(InjectorIm pl .java:609) at com.google.inject.internal.InjectorImpl.cleanup(InjectorImpl.java:565) at com.google.inject.internal.InjectorImpl.initializeJitBinding(InjectorImpl. ja va:551) at com.google.inject.internal.InjectorImpl.createJustInTimeBinding(InjectorIm pl .java:865) at com.google.inject.internal.InjectorImpl.createJustInTimeBindingRecursive(I nj ectorImpl.java:790) at com.google.inject.internal.InjectorImpl.getJustInTimeBinding(InjectorImpl. ja va:278) at com.google.inject.internal.InjectorImpl.getBindingOrThrow(InjectorImpl.java: 210) at com.google.inject.internal.InjectorImpl.getProviderOrThrow(InjectorImpl.ja va :986) at com.google.inject.internal.InjectorImpl.getProvider(InjectorImpl.java:1019 ) at com.google.inject.internal.InjectorImpl.getProvider(InjectorImpl.java:982) at com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:1032 ) at org.eclipse.sisu.reflect.AbstractDeferredClass.get(AbstractDeferredClass.j av a:44) at com.google.inject.internal.ProviderInternalFactory.provision(ProviderInter na lFactory.java:86) at com.google.inject.internal.InternalFactoryToInitializableAdapter.provision (I nternalFactoryToInitializableAdapter.java:55) at com.google.inject.internal.ProviderInternalFactory$1.call(ProviderInternal Fa ctory.java:70) at com.google.inject.internal.ProvisionListenerStackCallback$Provision.provis io n(ProvisionListenerStackCallback.java:100) at org.eclipse.sisu.plexus.lifecycles.PlexusLifecycleManager.onProvision(Plex us LifecycleManager.java:134) at com.google.inject.internal.ProvisionListenerStackCallback$Provision.provis io n(ProvisionListenerStackCallback.java:109) at com.google.inject.internal.ProvisionListenerStackCallback.provision(Provis io nListenerStackCallback.java:55) at com.google.inject.internal.ProviderInternalFactory.circularGet(ProviderInt er nalFactory.java:68) at
Re: [VOTE] Apache 3.1.0-alpha-1
I *think* that vote was also cancelled, isn't it? 2013/5/27 Hervé BOUTEMY herve.bout...@free.fr +1 works fine for me Regards, Hervé Le samedi 25 mai 2013 08:51:00 Jason van Zyl a écrit : Here are the release bits for 3.1.0-alpha-1: Release notes: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=18 967 Staging repository: https://repository.apache.org/content/repositories/maven-044/ Staged distribution: https://repository.apache.org/content/repositories/maven-044/org/apache/mave n/apache-maven/3.1.0-alpha-1/ Staged Site: http://maven.apache.org/ref/3.1.0-alpha-1 Thanks, Jason -- Jason van Zyl Founder CTO, Sonatype Founder, Apache Maven http://twitter.com/jvanzyl - We know what we are, but know not what we may be. -- Shakespeare - 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 -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
Re: [VOTE] Apache 3.1.0-alpha-1
I think staging 044 is the respin On 28 May 2013 08:10, Baptiste MATHUS bmat...@batmat.net wrote: I *think* that vote was also cancelled, isn't it? 2013/5/27 Hervé BOUTEMY herve.bout...@free.fr +1 works fine for me Regards, Hervé Le samedi 25 mai 2013 08:51:00 Jason van Zyl a écrit : Here are the release bits for 3.1.0-alpha-1: Release notes: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=18 967 Staging repository: https://repository.apache.org/content/repositories/maven-044/ Staged distribution: https://repository.apache.org/content/repositories/maven-044/org/apache/mave n/apache-maven/3.1.0-alpha-1/ Staged Site: http://maven.apache.org/ref/3.1.0-alpha-1 Thanks, Jason -- Jason van Zyl Founder CTO, Sonatype Founder, Apache Maven http://twitter.com/jvanzyl - We know what we are, but know not what we may be. -- Shakespeare - 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 -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
Re: [VOTE] Apache 3.1.0-alpha-1
OK, you're right. Jason's cancellation mail was http://mail-archives.apache.org/mod_mbox/maven-dev/201305.mbox/browser and is actually for -038. Gmail has merged threads for me so I mixed up things. Thanks 2013/5/28 Stephen Connolly stephen.alan.conno...@gmail.com I think staging 044 is the respin On 28 May 2013 08:10, Baptiste MATHUS bmat...@batmat.net wrote: I *think* that vote was also cancelled, isn't it? 2013/5/27 Hervé BOUTEMY herve.bout...@free.fr +1 works fine for me Regards, Hervé Le samedi 25 mai 2013 08:51:00 Jason van Zyl a écrit : Here are the release bits for 3.1.0-alpha-1: Release notes: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=18 967 Staging repository: https://repository.apache.org/content/repositories/maven-044/ Staged distribution: https://repository.apache.org/content/repositories/maven-044/org/apache/mave n/apache-maven/3.1.0-alpha-1/ Staged Site: http://maven.apache.org/ref/3.1.0-alpha-1 Thanks, Jason -- Jason van Zyl Founder CTO, Sonatype Founder, Apache Maven http://twitter.com/jvanzyl - We know what we are, but know not what we may be. -- Shakespeare - 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 -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor ! -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
Re: [VOTE] Apache 3.1.0-alpha-1
Tested on my Tycho (0.17.0 and latest staged 0.18.0) build and it fails but I think this is a Tycho issue. Regards Jeff On Tue, May 28, 2013 at 10:03 AM, Baptiste MATHUS bmat...@batmat.netwrote: OK, you're right. Jason's cancellation mail was http://mail-archives.apache.org/mod_mbox/maven-dev/201305.mbox/browser and is actually for -038. Gmail has merged threads for me so I mixed up things. Thanks 2013/5/28 Stephen Connolly stephen.alan.conno...@gmail.com I think staging 044 is the respin On 28 May 2013 08:10, Baptiste MATHUS bmat...@batmat.net wrote: I *think* that vote was also cancelled, isn't it? 2013/5/27 Hervé BOUTEMY herve.bout...@free.fr +1 works fine for me Regards, Hervé Le samedi 25 mai 2013 08:51:00 Jason van Zyl a écrit : Here are the release bits for 3.1.0-alpha-1: Release notes: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=18 967 Staging repository: https://repository.apache.org/content/repositories/maven-044/ Staged distribution: https://repository.apache.org/content/repositories/maven-044/org/apache/mave n/apache-maven/3.1.0-alpha-1/ Staged Site: http://maven.apache.org/ref/3.1.0-alpha-1 Thanks, Jason -- Jason van Zyl Founder CTO, Sonatype Founder, Apache Maven http://twitter.com/jvanzyl - We know what we are, but know not what we may be. -- Shakespeare - 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 -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor ! -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor ! -- Jeff MAURY Legacy code often differs from its suggested alternative by actually working and scaling. - Bjarne Stroustrup http://www.jeffmaury.com http://riadiscuss.jeffmaury.com http://www.twitter.com/jeffmaury
RE: [VOTE] Apache 3.1.0-alpha-1
https://bugs.eclipse.org/bugs/show_bug.cgi?id=406056 will try to fix this with the next tycho release once 3.1.0-alpha-1 is out Regards Jan -Original Message- From: jeffma...@gmail.com [mailto:jeffma...@gmail.com] On Behalf Of Jeff MAURY Sent: Dienstag, 28. Mai 2013 10:15 To: Maven Developers List Subject: Re: [VOTE] Apache 3.1.0-alpha-1 Tested on my Tycho (0.17.0 and latest staged 0.18.0) build and it fails but I think this is a Tycho issue. Regards Jeff On Tue, May 28, 2013 at 10:03 AM, Baptiste MATHUS bmat...@batmat.netwrote: OK, you're right. Jason's cancellation mail was http://mail-archives.apache.org/mod_mbox/maven-dev/201305.mbox/browser and is actually for -038. Gmail has merged threads for me so I mixed up things. Thanks 2013/5/28 Stephen Connolly stephen.alan.conno...@gmail.com I think staging 044 is the respin On 28 May 2013 08:10, Baptiste MATHUS bmat...@batmat.net wrote: I *think* that vote was also cancelled, isn't it? 2013/5/27 Hervé BOUTEMY herve.bout...@free.fr +1 works fine for me Regards, Hervé Le samedi 25 mai 2013 08:51:00 Jason van Zyl a écrit : Here are the release bits for 3.1.0-alpha-1: Release notes: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=18 967 Staging repository: https://repository.apache.org/content/repositories/maven-044/ Staged distribution: https://repository.apache.org/content/repositories/maven-044/org/apache/mave n/apache-maven/3.1.0-alpha-1/ Staged Site: http://maven.apache.org/ref/3.1.0-alpha-1 Thanks, Jason -- Jason van Zyl Founder CTO, Sonatype Founder, Apache Maven http://twitter.com/jvanzyl - We know what we are, but know not what we may be. -- Shakespeare - 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 -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor ! -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor ! -- Jeff MAURY Legacy code often differs from its suggested alternative by actually working and scaling. - Bjarne Stroustrup http://www.jeffmaury.com http://riadiscuss.jeffmaury.com http://www.twitter.com/jeffmaury - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Apache 3.1.0-alpha-1
[x] Builds from source bundle [x] Builds some complex projects [x] Contains correct LICENSE.txt [ ] NOTICE.txt correctly attributes 3rd party components (See observation 1) [?] All source files, where appropriate, contain the ASL header (See observation 2) [?] Binary archives bundled within the source distribution (See observation 3) On the basis of the NOTICE.txt not acknowledging Eclipse Aether, and only on that basis I will be voting -0.9 (binding) The other issues are non-critical but it would be nice to tidy them up... nice to have. Observations 1. No attribution of Eclipse Aether, only referenced as developed by Sonatype. 2. The following 39 files are missing license headers: apache-maven/src/bin/m2.conf apache-maven/src/conf/logging/simplelogger.properties maven-aether-provider/src/main/java/org/apache/maven/repository/internal/package.html maven-aether-provider/src/site/apt/index.apt maven-artifact/src/site/apt/index.apt maven-compat/compatibility.cfl maven-compat/src/main/resources/META-INF/maven/plugin.xml maven-core/lifecycle-executor.txt maven-core/plugin-manager.txt maven-core/project-builder.txt maven-core/src/main/resources/org/apache/maven/messages/build.properties maven-core/src/site/apt/artifact-handlers.apt maven-core/src/site/apt/configuration-management.apt maven-core/src/site/apt/default-bindings.apt.vm maven-core/src/site/apt/getting-to-container-configured-mojos.apt maven-core/src/site/apt/index.apt maven-core/src/site/apt/inheritance.apt maven-core/src/site/apt/lifecycles.apt.vm maven-core/src/site/apt/offline-mode.apt maven-core/src/site/apt/plugin-execution-isolation.apt maven-core/src/site/apt/scripting-support/marmalade-support.apt maven-core/src/site/resources/design/2.1-lifecycle-refactor.graffle maven-embedder/src/examples/simple-project/src/main/java/org/apache/maven/embedder/App.java maven-embedder/src/examples/simple-project/src/test/java/org/apache/maven/embedder/AppTest.java maven-embedder/src/main/resources/META-INF/MANIFEST.MF maven-embedder/src/main/resources/META-INF/maven/slf4j-configuration.properties maven-embedder/src/site/apt/cli.apt.vm maven-embedder/src/site/apt/index.apt.vm maven-embedder/src/site/apt/logging.apt maven-model-builder/src/site/apt/index.apt maven-model-builder/src/site/apt/super-pom.apt.vm maven-model/src/main/java/org/apache/maven/model/io/xpp3/package.html maven-model/src/main/java/org/apache/maven/model/merge/package.html maven-model/src/main/java/org/apache/maven/model/package.html maven-model/src/site/apt/index.apt maven-plugin-api/src/site/apt/index.apt maven-repository-metadata/src/site/apt/index.apt maven-settings/src/site/apt/index.apt README.bootstrap.txt None of these are actual production code, so I don't see this as a blocker for release, but it would be good to tidy them up. Additionally, the embedder examples should have their license explicitly stated to remove confusion for anyone pegging the examples to build their own code upon. In addition I note that there are 432 test resources that do not have a license header, however, as test resources it is legitimate to argue that the license header could affect the test. It would be good if we could get that number reduced, but only if we are confident that we are not introducing false test passes in the process. 3. There is one (non-test) archive bundled within the distribution: maven-ant-tasks-2.1.1.jar Given that this specific artifact suffers from the bootstrap issue (i.e. it needs Maven to build it) and the source is available and this artifact is not part of the built code, but rather the build process, I am unclear as to what the legal requirement for including this in the source distribution. It would be nice if we had some clarity on the artifact. OTOH it is code under the ASL and the NOTICE.txt perhaps covers it. On 25 May 2013 13:51, Jason van Zyl ja...@tesla.io wrote: Here are the release bits for 3.1.0-alpha-1: Release notes: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=18967 Staging repository: https://repository.apache.org/content/repositories/maven-044/ Staged distribution: https://repository.apache.org/content/repositories/maven-044/org/apache/maven/apache-maven/3.1.0-alpha-1/ Staged Site: http://maven.apache.org/ref/3.1.0-alpha-1 Thanks, Jason -- Jason van Zyl Founder CTO, Sonatype Founder, Apache Maven http://twitter.com/jvanzyl - We know what we are, but know not what we may be. -- Shakespeare - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail:
Re: [VOTE] Apache 3.1.0-alpha-1
For now I had no issue with this release after an upgrade of few plugins In the future (another Alpha ..) couldn't you catch such error and provide a more user friendly message asking to upgrade the plugin : [INFO] Dependency-reduced POM written at: /Users/arnaud/Code/eXo/platform-public-distributions/plf-tomcat-extensions-manager/dependency-reduced-pom.xml [WARNING] Error injecting: org.apache.maven.shared.dependency.graph.internal.Maven3DependencyGraphBuilder java.lang.NoClassDefFoundError: org/sonatype/aether/graph/Dependency at java.lang.Class.getDeclaredMethods0(Native Method) at java.lang.Class.privateGetDeclaredMethods(Class.java:2436) at java.lang.Class.getDeclaredMethods(Class.java:1793) at com.google.inject.spi.InjectionPoint.getInjectionPoints(InjectionPoint.java:674) at com.google.inject.spi.InjectionPoint.forInstanceMethodsAndFields(InjectionPoint.java:366) at com.google.inject.internal.ConstructorBindingImpl.getInternalDependencies(ConstructorBindingImpl.java:165) at com.google.inject.internal.InjectorImpl.getInternalDependencies(InjectorImpl.java:609) at com.google.inject.internal.InjectorImpl.cleanup(InjectorImpl.java:565) at com.google.inject.internal.InjectorImpl.initializeJitBinding(InjectorImpl.java:551) at com.google.inject.internal.InjectorImpl.createJustInTimeBinding(InjectorImpl.java:865) at com.google.inject.internal.InjectorImpl.createJustInTimeBindingRecursive(InjectorImpl.java:790) at com.google.inject.internal.InjectorImpl.getJustInTimeBinding(InjectorImpl.java:278) at com.google.inject.internal.InjectorImpl.getBindingOrThrow(InjectorImpl.java:210) at com.google.inject.internal.InjectorImpl.getProviderOrThrow(InjectorImpl.java:986) at com.google.inject.internal.InjectorImpl.getProvider(InjectorImpl.java:1019) at com.google.inject.internal.InjectorImpl.getProvider(InjectorImpl.java:982) at com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:1032) at org.eclipse.sisu.reflect.AbstractDeferredClass.get(AbstractDeferredClass.java:44) at com.google.inject.internal.ProviderInternalFactory.provision(ProviderInternalFactory.java:86) at com.google.inject.internal.InternalFactoryToInitializableAdapter.provision(InternalFactoryToInitializableAdapter.java:55) at com.google.inject.internal.ProviderInternalFactory$1.call(ProviderInternalFactory.java:70) at com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:100) at org.eclipse.sisu.plexus.lifecycles.PlexusLifecycleManager.onProvision(PlexusLifecycleManager.java:134) at com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:109) at com.google.inject.internal.ProvisionListenerStackCallback.provision(ProvisionListenerStackCallback.java:55) at com.google.inject.internal.ProviderInternalFactory.circularGet(ProviderInternalFactory.java:68) at com.google.inject.internal.InternalFactoryToInitializableAdapter.get(InternalFactoryToInitializableAdapter.java:47) at com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46) at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1054) at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40) at com.google.inject.Scopes$1$1.get(Scopes.java:59) at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41) at com.google.inject.internal.InjectorImpl$2$1.call(InjectorImpl.java:997) at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1047) at com.google.inject.internal.InjectorImpl$2.get(InjectorImpl.java:993) at org.eclipse.sisu.locators.LazyBeanEntry.getValue(LazyBeanEntry.java:82) at org.eclipse.sisu.plexus.locators.LazyPlexusBean.getValue(LazyPlexusBean.java:52) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:259) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:239) at org.apache.maven.shared.dependency.graph.internal.DefaultDependencyGraphBuilder.buildDependencyGraph(DefaultDependencyGraphBuilder.java:60) at org.apache.maven.plugins.shade.mojo.ShadeMojo.updateExcludesInDeps(ShadeMojo.java:965) at org.apache.maven.plugins.shade.mojo.ShadeMojo.createDependencyReducedPom(ShadeMojo.java:938) at org.apache.maven.plugins.shade.mojo.ShadeMojo.execute(ShadeMojo.java:544) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:105) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at
Re: [VOTE] Apache 3.1.0-alpha-1
Would it help to catch NoClassDefFoundError DefaultBuildPluginManager.executeMojo and if it's anything in the org/sonatype/aether/ space, give a warning about requiring newer plugin? Kristian 2013/5/28 Arnaud Héritier aherit...@gmail.com: For now I had no issue with this release after an upgrade of few plugins In the future (another Alpha ..) couldn't you catch such error and provide a more user friendly message asking to upgrade the plugin : [INFO] Dependency-reduced POM written at: /Users/arnaud/Code/eXo/platform-public-distributions/plf-tomcat-extensions-manager/dependency-reduced-pom.xml [WARNING] Error injecting: org.apache.maven.shared.dependency.graph.internal.Maven3DependencyGraphBuilder java.lang.NoClassDefFoundError: org/sonatype/aether/graph/Dependency at java.lang.Class.getDeclaredMethods0(Native Method) at java.lang.Class.privateGetDeclaredMethods(Class.java:2436) at java.lang.Class.getDeclaredMethods(Class.java:1793) at com.google.inject.spi.InjectionPoint.getInjectionPoints(InjectionPoint.java:674) at com.google.inject.spi.InjectionPoint.forInstanceMethodsAndFields(InjectionPoint.java:366) at com.google.inject.internal.ConstructorBindingImpl.getInternalDependencies(ConstructorBindingImpl.java:165) at com.google.inject.internal.InjectorImpl.getInternalDependencies(InjectorImpl.java:609) at com.google.inject.internal.InjectorImpl.cleanup(InjectorImpl.java:565) at com.google.inject.internal.InjectorImpl.initializeJitBinding(InjectorImpl.java:551) at com.google.inject.internal.InjectorImpl.createJustInTimeBinding(InjectorImpl.java:865) at com.google.inject.internal.InjectorImpl.createJustInTimeBindingRecursive(InjectorImpl.java:790) at com.google.inject.internal.InjectorImpl.getJustInTimeBinding(InjectorImpl.java:278) at com.google.inject.internal.InjectorImpl.getBindingOrThrow(InjectorImpl.java:210) at com.google.inject.internal.InjectorImpl.getProviderOrThrow(InjectorImpl.java:986) at com.google.inject.internal.InjectorImpl.getProvider(InjectorImpl.java:1019) at com.google.inject.internal.InjectorImpl.getProvider(InjectorImpl.java:982) at com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:1032) at org.eclipse.sisu.reflect.AbstractDeferredClass.get(AbstractDeferredClass.java:44) at com.google.inject.internal.ProviderInternalFactory.provision(ProviderInternalFactory.java:86) at com.google.inject.internal.InternalFactoryToInitializableAdapter.provision(InternalFactoryToInitializableAdapter.java:55) at com.google.inject.internal.ProviderInternalFactory$1.call(ProviderInternalFactory.java:70) at com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:100) at org.eclipse.sisu.plexus.lifecycles.PlexusLifecycleManager.onProvision(PlexusLifecycleManager.java:134) at com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:109) at com.google.inject.internal.ProvisionListenerStackCallback.provision(ProvisionListenerStackCallback.java:55) at com.google.inject.internal.ProviderInternalFactory.circularGet(ProviderInternalFactory.java:68) at com.google.inject.internal.InternalFactoryToInitializableAdapter.get(InternalFactoryToInitializableAdapter.java:47) at com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46) at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1054) at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40) at com.google.inject.Scopes$1$1.get(Scopes.java:59) at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41) at com.google.inject.internal.InjectorImpl$2$1.call(InjectorImpl.java:997) at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1047) at com.google.inject.internal.InjectorImpl$2.get(InjectorImpl.java:993) at org.eclipse.sisu.locators.LazyBeanEntry.getValue(LazyBeanEntry.java:82) at org.eclipse.sisu.plexus.locators.LazyPlexusBean.getValue(LazyPlexusBean.java:52) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:259) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:239) at org.apache.maven.shared.dependency.graph.internal.DefaultDependencyGraphBuilder.buildDependencyGraph(DefaultDependencyGraphBuilder.java:60) at org.apache.maven.plugins.shade.mojo.ShadeMojo.updateExcludesInDeps(ShadeMojo.java:965) at org.apache.maven.plugins.shade.mojo.ShadeMojo.createDependencyReducedPom(ShadeMojo.java:938) at org.apache.maven.plugins.shade.mojo.ShadeMojo.execute(ShadeMojo.java:544) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:105) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) at
Re: [VOTE] Apache 3.1.0-alpha-1
One small comment regarding the packaging.html files: IMO any package.html under src/main/java should be replaced package-info.java, because it doesn't make sense to have html-files between the java-sources. Robert Op Tue, 28 May 2013 10:38:07 +0200 schreef Stephen Connolly stephen.alan.conno...@gmail.com: [x] Builds from source bundle [x] Builds some complex projects [x] Contains correct LICENSE.txt [ ] NOTICE.txt correctly attributes 3rd party components (See observation 1) [?] All source files, where appropriate, contain the ASL header (See observation 2) [?] Binary archives bundled within the source distribution (See observation 3) On the basis of the NOTICE.txt not acknowledging Eclipse Aether, and only on that basis I will be voting -0.9 (binding) The other issues are non-critical but it would be nice to tidy them up... nice to have. Observations 1. No attribution of Eclipse Aether, only referenced as developed by Sonatype. 2. The following 39 files are missing license headers: apache-maven/src/bin/m2.conf apache-maven/src/conf/logging/simplelogger.properties maven-aether-provider/src/main/java/org/apache/maven/repository/internal/package.html maven-aether-provider/src/site/apt/index.apt maven-artifact/src/site/apt/index.apt maven-compat/compatibility.cfl maven-compat/src/main/resources/META-INF/maven/plugin.xml maven-core/lifecycle-executor.txt maven-core/plugin-manager.txt maven-core/project-builder.txt maven-core/src/main/resources/org/apache/maven/messages/build.properties maven-core/src/site/apt/artifact-handlers.apt maven-core/src/site/apt/configuration-management.apt maven-core/src/site/apt/default-bindings.apt.vm maven-core/src/site/apt/getting-to-container-configured-mojos.apt maven-core/src/site/apt/index.apt maven-core/src/site/apt/inheritance.apt maven-core/src/site/apt/lifecycles.apt.vm maven-core/src/site/apt/offline-mode.apt maven-core/src/site/apt/plugin-execution-isolation.apt maven-core/src/site/apt/scripting-support/marmalade-support.apt maven-core/src/site/resources/design/2.1-lifecycle-refactor.graffle maven-embedder/src/examples/simple-project/src/main/java/org/apache/maven/embedder/App.java maven-embedder/src/examples/simple-project/src/test/java/org/apache/maven/embedder/AppTest.java maven-embedder/src/main/resources/META-INF/MANIFEST.MF maven-embedder/src/main/resources/META-INF/maven/slf4j-configuration.properties maven-embedder/src/site/apt/cli.apt.vm maven-embedder/src/site/apt/index.apt.vm maven-embedder/src/site/apt/logging.apt maven-model-builder/src/site/apt/index.apt maven-model-builder/src/site/apt/super-pom.apt.vm maven-model/src/main/java/org/apache/maven/model/io/xpp3/package.html maven-model/src/main/java/org/apache/maven/model/merge/package.html maven-model/src/main/java/org/apache/maven/model/package.html maven-model/src/site/apt/index.apt maven-plugin-api/src/site/apt/index.apt maven-repository-metadata/src/site/apt/index.apt maven-settings/src/site/apt/index.apt README.bootstrap.txt None of these are actual production code, so I don't see this as a blocker for release, but it would be good to tidy them up. Additionally, the embedder examples should have their license explicitly stated to remove confusion for anyone pegging the examples to build their own code upon. In addition I note that there are 432 test resources that do not have a license header, however, as test resources it is legitimate to argue that the license header could affect the test. It would be good if we could get that number reduced, but only if we are confident that we are not introducing false test passes in the process. 3. There is one (non-test) archive bundled within the distribution: maven-ant-tasks-2.1.1.jar Given that this specific artifact suffers from the bootstrap issue (i.e. it needs Maven to build it) and the source is available and this artifact is not part of the built code, but rather the build process, I am unclear as to what the legal requirement for including this in the source distribution. It would be nice if we had some clarity on the artifact. OTOH it is code under the ASL and the NOTICE.txt perhaps covers it. On 25 May 2013 13:51, Jason van Zyl ja...@tesla.io wrote: Here are the release bits for 3.1.0-alpha-1: Release notes: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=18967 Staging repository: https://repository.apache.org/content/repositories/maven-044/ Staged distribution: https://repository.apache.org/content/repositories/maven-044/org/apache/maven/apache-maven/3.1.0-alpha-1/ Staged Site: http://maven.apache.org/ref/3.1.0-alpha-1 Thanks, Jason -- Jason van Zyl Founder CTO, Sonatype Founder, Apache Maven http://twitter.com/jvanzyl - We know what we are, but know not what we may be. --
Re: [VOTE] Apache 3.1.0-alpha-1
Go for it. I committed the license header fix-ups Not sure myself what the exact wording is that should go in the NOTICE.txt but I know it is wrong... Therefore AIUI that is a blocker for the PMC permitting the release as is... In any case if the rest of the PMC do not see it as a blocker might as well get the package-info.java in place for the next alpha or the RC On Tuesday, 28 May 2013, Robert Scholte wrote: One small comment regarding the packaging.html files: IMO any package.html under src/main/java should be replaced package-info.java, because it doesn't make sense to have html-files between the java-sources. Robert Op Tue, 28 May 2013 10:38:07 +0200 schreef Stephen Connolly stephen.alan.conno...@gmail.com: [x] Builds from source bundle [x] Builds some complex projects [x] Contains correct LICENSE.txt [ ] NOTICE.txt correctly attributes 3rd party components (See observation 1) [?] All source files, where appropriate, contain the ASL header (See observation 2) [?] Binary archives bundled within the source distribution (See observation 3) On the basis of the NOTICE.txt not acknowledging Eclipse Aether, and only on that basis I will be voting -0.9 (binding) The other issues are non-critical but it would be nice to tidy them up... nice to have. Observations 1. No attribution of Eclipse Aether, only referenced as developed by Sonatype. 2. The following 39 files are missing license headers: apache-maven/src/bin/m2.conf apache-maven/src/conf/logging/**simplelogger.properties maven-aether-provider/src/**main/java/org/apache/maven/** repository/internal/package.**html maven-aether-provider/src/**site/apt/index.apt maven-artifact/src/site/apt/**index.apt maven-compat/compatibility.cfl maven-compat/src/main/**resources/META-INF/maven/**plugin.xml maven-core/lifecycle-executor.**txt maven-core/plugin-manager.txt maven-core/project-builder.txt maven-core/src/main/resources/**org/apache/maven/messages/** build.properties maven-core/src/site/apt/**artifact-handlers.apt maven-core/src/site/apt/**configuration-management.apt maven-core/src/site/apt/**default-bindings.apt.vm maven-core/src/site/apt/**getting-to-container-**configured-mojos.apt maven-core/src/site/apt/index.**apt maven-core/src/site/apt/**inheritance.apt maven-core/src/site/apt/**lifecycles.apt.vm maven-core/src/site/apt/**offline-mode.apt maven-core/src/site/apt/**plugin-execution-isolation.apt maven-core/src/site/apt/**scripting-support/marmalade-**support.apt maven-core/src/site/resources/**design/2.1-lifecycle-refactor.**graffle maven-embedder/src/examples/**simple-project/src/main/java/** org/apache/maven/embedder/App.**java maven-embedder/src/examples/**simple-project/src/test/java/** org/apache/maven/embedder/**AppTest.java maven-embedder/src/main/**resources/META-INF/MANIFEST.MF maven-embedder/src/main/**resources/META-INF/maven/** slf4j-configuration.properties maven-embedder/src/site/apt/**cli.apt.vm maven-embedder/src/site/apt/**index.apt.vm maven-embedder/src/site/apt/**logging.apt maven-model-builder/src/site/**apt/index.apt maven-model-builder/src/site/**apt/super-pom.apt.vm maven-model/src/main/java/org/**apache/maven/model/io/xpp3/** package.html maven-model/src/main/java/org/**apache/maven/model/merge/**package.html maven-model/src/main/java/org/**apache/maven/model/package.**html maven-model/src/site/apt/**index.apt maven-plugin-api/src/site/apt/**index.apt maven-repository-metadata/src/**site/apt/index.apt maven-settings/src/site/apt/**index.apt README.bootstrap.txt None of these are actual production code, so I don't see this as a blocker for release, but it would be good to tidy them up. Additionally, the embedder examples should have their license explicitly stated to remove confusion for anyone pegging the examples to build their own code upon. In addition I note that there are 432 test resources that do not have a license header, however, as test resources it is legitimate to argue that the license header could affect the test. It would be good if we could get that number reduced, but only if we are confident that we are not introducing false test passes in the process. 3. There is one (non-test) archive bundled within the distribution: maven-ant-tasks-2.1.1.jar Given that this specific artifact suffers from the bootstrap issue (i.e. it needs Maven to build it) and the source is available and this artifact is not part of the built code, but rather the build process, I am unclear as to what the legal requirement for including this in the source distribution. It would be nice if we had some clarity on the artifact. OTOH it is code under the ASL and the NOTICE.txt perhaps covers it. On 25 May 2013 13:51, Jason van Zyl ja...@tesla.io wrote: -- Sent from my phone
Re: [VOTE] Apache 3.1.0-alpha-1
Done, see http://git-wip-us.apache.org/repos/asf/maven/commit/e1807abf Op Tue, 28 May 2013 21:02:24 +0200 schreef Stephen Connolly stephen.alan.conno...@gmail.com: Go for it. I committed the license header fix-ups Not sure myself what the exact wording is that should go in the NOTICE.txt but I know it is wrong... Therefore AIUI that is a blocker for the PMC permitting the release as is... In any case if the rest of the PMC do not see it as a blocker might as well get the package-info.java in place for the next alpha or the RC On Tuesday, 28 May 2013, Robert Scholte wrote: One small comment regarding the packaging.html files: IMO any package.html under src/main/java should be replaced package-info.java, because it doesn't make sense to have html-files between the java-sources. Robert Op Tue, 28 May 2013 10:38:07 +0200 schreef Stephen Connolly stephen.alan.conno...@gmail.com: [x] Builds from source bundle [x] Builds some complex projects [x] Contains correct LICENSE.txt [ ] NOTICE.txt correctly attributes 3rd party components (See observation 1) [?] All source files, where appropriate, contain the ASL header (See observation 2) [?] Binary archives bundled within the source distribution (See observation 3) On the basis of the NOTICE.txt not acknowledging Eclipse Aether, and only on that basis I will be voting -0.9 (binding) The other issues are non-critical but it would be nice to tidy them up... nice to have. Observations 1. No attribution of Eclipse Aether, only referenced as developed by Sonatype. 2. The following 39 files are missing license headers: apache-maven/src/bin/m2.conf apache-maven/src/conf/logging/**simplelogger.properties maven-aether-provider/src/**main/java/org/apache/maven/** repository/internal/package.**html maven-aether-provider/src/**site/apt/index.apt maven-artifact/src/site/apt/**index.apt maven-compat/compatibility.cfl maven-compat/src/main/**resources/META-INF/maven/**plugin.xml maven-core/lifecycle-executor.**txt maven-core/plugin-manager.txt maven-core/project-builder.txt maven-core/src/main/resources/**org/apache/maven/messages/** build.properties maven-core/src/site/apt/**artifact-handlers.apt maven-core/src/site/apt/**configuration-management.apt maven-core/src/site/apt/**default-bindings.apt.vm maven-core/src/site/apt/**getting-to-container-**configured-mojos.apt maven-core/src/site/apt/index.**apt maven-core/src/site/apt/**inheritance.apt maven-core/src/site/apt/**lifecycles.apt.vm maven-core/src/site/apt/**offline-mode.apt maven-core/src/site/apt/**plugin-execution-isolation.apt maven-core/src/site/apt/**scripting-support/marmalade-**support.apt maven-core/src/site/resources/**design/2.1-lifecycle-refactor.**graffle maven-embedder/src/examples/**simple-project/src/main/java/** org/apache/maven/embedder/App.**java maven-embedder/src/examples/**simple-project/src/test/java/** org/apache/maven/embedder/**AppTest.java maven-embedder/src/main/**resources/META-INF/MANIFEST.MF maven-embedder/src/main/**resources/META-INF/maven/** slf4j-configuration.properties maven-embedder/src/site/apt/**cli.apt.vm maven-embedder/src/site/apt/**index.apt.vm maven-embedder/src/site/apt/**logging.apt maven-model-builder/src/site/**apt/index.apt maven-model-builder/src/site/**apt/super-pom.apt.vm maven-model/src/main/java/org/**apache/maven/model/io/xpp3/** package.html maven-model/src/main/java/org/**apache/maven/model/merge/**package.html maven-model/src/main/java/org/**apache/maven/model/package.**html maven-model/src/site/apt/**index.apt maven-plugin-api/src/site/apt/**index.apt maven-repository-metadata/src/**site/apt/index.apt maven-settings/src/site/apt/**index.apt README.bootstrap.txt None of these are actual production code, so I don't see this as a blocker for release, but it would be good to tidy them up. Additionally, the embedder examples should have their license explicitly stated to remove confusion for anyone pegging the examples to build their own code upon. In addition I note that there are 432 test resources that do not have a license header, however, as test resources it is legitimate to argue that the license header could affect the test. It would be good if we could get that number reduced, but only if we are confident that we are not introducing false test passes in the process. 3. There is one (non-test) archive bundled within the distribution: maven-ant-tasks-2.1.1.jar Given that this specific artifact suffers from the bootstrap issue (i.e. it needs Maven to build it) and the source is available and this artifact is not part of the built code, but rather the build process, I am unclear as to what the legal requirement for including this in the source distribution. It would be nice if we had some clarity on the artifact. OTOH it is code under the ASL and the NOTICE.txt perhaps covers it. On 25 May 2013 13:51, Jason van Zyl
Re: [VOTE] Apache 3.1.0-alpha-1
Some additional remarks: - The copyright doesn't include current year (I've already fixed that on the trunk) - doap:generate fails: The generated DOAP doesn't respect ASF rules. Just to be sure I understand correctly: these alpha-versions will never be released. They are created so users can try them. -1 votes would mean it is not yet ready for a beta or final release. Is this right? Robert Op Tue, 28 May 2013 10:38:07 +0200 schreef Stephen Connolly stephen.alan.conno...@gmail.com: [x] Builds from source bundle [x] Builds some complex projects [x] Contains correct LICENSE.txt [ ] NOTICE.txt correctly attributes 3rd party components (See observation 1) [?] All source files, where appropriate, contain the ASL header (See observation 2) [?] Binary archives bundled within the source distribution (See observation 3) On the basis of the NOTICE.txt not acknowledging Eclipse Aether, and only on that basis I will be voting -0.9 (binding) The other issues are non-critical but it would be nice to tidy them up... nice to have. Observations 1. No attribution of Eclipse Aether, only referenced as developed by Sonatype. 2. The following 39 files are missing license headers: apache-maven/src/bin/m2.conf apache-maven/src/conf/logging/simplelogger.properties maven-aether-provider/src/main/java/org/apache/maven/repository/internal/package.html maven-aether-provider/src/site/apt/index.apt maven-artifact/src/site/apt/index.apt maven-compat/compatibility.cfl maven-compat/src/main/resources/META-INF/maven/plugin.xml maven-core/lifecycle-executor.txt maven-core/plugin-manager.txt maven-core/project-builder.txt maven-core/src/main/resources/org/apache/maven/messages/build.properties maven-core/src/site/apt/artifact-handlers.apt maven-core/src/site/apt/configuration-management.apt maven-core/src/site/apt/default-bindings.apt.vm maven-core/src/site/apt/getting-to-container-configured-mojos.apt maven-core/src/site/apt/index.apt maven-core/src/site/apt/inheritance.apt maven-core/src/site/apt/lifecycles.apt.vm maven-core/src/site/apt/offline-mode.apt maven-core/src/site/apt/plugin-execution-isolation.apt maven-core/src/site/apt/scripting-support/marmalade-support.apt maven-core/src/site/resources/design/2.1-lifecycle-refactor.graffle maven-embedder/src/examples/simple-project/src/main/java/org/apache/maven/embedder/App.java maven-embedder/src/examples/simple-project/src/test/java/org/apache/maven/embedder/AppTest.java maven-embedder/src/main/resources/META-INF/MANIFEST.MF maven-embedder/src/main/resources/META-INF/maven/slf4j-configuration.properties maven-embedder/src/site/apt/cli.apt.vm maven-embedder/src/site/apt/index.apt.vm maven-embedder/src/site/apt/logging.apt maven-model-builder/src/site/apt/index.apt maven-model-builder/src/site/apt/super-pom.apt.vm maven-model/src/main/java/org/apache/maven/model/io/xpp3/package.html maven-model/src/main/java/org/apache/maven/model/merge/package.html maven-model/src/main/java/org/apache/maven/model/package.html maven-model/src/site/apt/index.apt maven-plugin-api/src/site/apt/index.apt maven-repository-metadata/src/site/apt/index.apt maven-settings/src/site/apt/index.apt README.bootstrap.txt None of these are actual production code, so I don't see this as a blocker for release, but it would be good to tidy them up. Additionally, the embedder examples should have their license explicitly stated to remove confusion for anyone pegging the examples to build their own code upon. In addition I note that there are 432 test resources that do not have a license header, however, as test resources it is legitimate to argue that the license header could affect the test. It would be good if we could get that number reduced, but only if we are confident that we are not introducing false test passes in the process. 3. There is one (non-test) archive bundled within the distribution: maven-ant-tasks-2.1.1.jar Given that this specific artifact suffers from the bootstrap issue (i.e. it needs Maven to build it) and the source is available and this artifact is not part of the built code, but rather the build process, I am unclear as to what the legal requirement for including this in the source distribution. It would be nice if we had some clarity on the artifact. OTOH it is code under the ASL and the NOTICE.txt perhaps covers it. On 25 May 2013 13:51, Jason van Zyl ja...@tesla.io wrote: Here are the release bits for 3.1.0-alpha-1: Release notes: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=18967 Staging repository: https://repository.apache.org/content/repositories/maven-044/ Staged distribution: https://repository.apache.org/content/repositories/maven-044/org/apache/maven/apache-maven/3.1.0-alpha-1/ Staged Site: http://maven.apache.org/ref/3.1.0-alpha-1 Thanks, Jason -- Jason van Zyl
Re: [VOTE] Apache 3.1.0-alpha-1
It's very easy to cut another release. If all the fixes are in that the PMC wishes it takes minutes to roll the release again. On May 28, 2013, at 4:43 PM, Robert Scholte rfscho...@apache.org wrote: Some additional remarks: - The copyright doesn't include current year (I've already fixed that on the trunk) - doap:generate fails: The generated DOAP doesn't respect ASF rules. Just to be sure I understand correctly: these alpha-versions will never be released. They are created so users can try them. -1 votes would mean it is not yet ready for a beta or final release. Is this right? Robert Op Tue, 28 May 2013 10:38:07 +0200 schreef Stephen Connolly stephen.alan.conno...@gmail.com: [x] Builds from source bundle [x] Builds some complex projects [x] Contains correct LICENSE.txt [ ] NOTICE.txt correctly attributes 3rd party components (See observation 1) [?] All source files, where appropriate, contain the ASL header (See observation 2) [?] Binary archives bundled within the source distribution (See observation 3) On the basis of the NOTICE.txt not acknowledging Eclipse Aether, and only on that basis I will be voting -0.9 (binding) The other issues are non-critical but it would be nice to tidy them up... nice to have. Observations 1. No attribution of Eclipse Aether, only referenced as developed by Sonatype. 2. The following 39 files are missing license headers: apache-maven/src/bin/m2.conf apache-maven/src/conf/logging/simplelogger.properties maven-aether-provider/src/main/java/org/apache/maven/repository/internal/package.html maven-aether-provider/src/site/apt/index.apt maven-artifact/src/site/apt/index.apt maven-compat/compatibility.cfl maven-compat/src/main/resources/META-INF/maven/plugin.xml maven-core/lifecycle-executor.txt maven-core/plugin-manager.txt maven-core/project-builder.txt maven-core/src/main/resources/org/apache/maven/messages/build.properties maven-core/src/site/apt/artifact-handlers.apt maven-core/src/site/apt/configuration-management.apt maven-core/src/site/apt/default-bindings.apt.vm maven-core/src/site/apt/getting-to-container-configured-mojos.apt maven-core/src/site/apt/index.apt maven-core/src/site/apt/inheritance.apt maven-core/src/site/apt/lifecycles.apt.vm maven-core/src/site/apt/offline-mode.apt maven-core/src/site/apt/plugin-execution-isolation.apt maven-core/src/site/apt/scripting-support/marmalade-support.apt maven-core/src/site/resources/design/2.1-lifecycle-refactor.graffle maven-embedder/src/examples/simple-project/src/main/java/org/apache/maven/embedder/App.java maven-embedder/src/examples/simple-project/src/test/java/org/apache/maven/embedder/AppTest.java maven-embedder/src/main/resources/META-INF/MANIFEST.MF maven-embedder/src/main/resources/META-INF/maven/slf4j-configuration.properties maven-embedder/src/site/apt/cli.apt.vm maven-embedder/src/site/apt/index.apt.vm maven-embedder/src/site/apt/logging.apt maven-model-builder/src/site/apt/index.apt maven-model-builder/src/site/apt/super-pom.apt.vm maven-model/src/main/java/org/apache/maven/model/io/xpp3/package.html maven-model/src/main/java/org/apache/maven/model/merge/package.html maven-model/src/main/java/org/apache/maven/model/package.html maven-model/src/site/apt/index.apt maven-plugin-api/src/site/apt/index.apt maven-repository-metadata/src/site/apt/index.apt maven-settings/src/site/apt/index.apt README.bootstrap.txt None of these are actual production code, so I don't see this as a blocker for release, but it would be good to tidy them up. Additionally, the embedder examples should have their license explicitly stated to remove confusion for anyone pegging the examples to build their own code upon. In addition I note that there are 432 test resources that do not have a license header, however, as test resources it is legitimate to argue that the license header could affect the test. It would be good if we could get that number reduced, but only if we are confident that we are not introducing false test passes in the process. 3. There is one (non-test) archive bundled within the distribution: maven-ant-tasks-2.1.1.jar Given that this specific artifact suffers from the bootstrap issue (i.e. it needs Maven to build it) and the source is available and this artifact is not part of the built code, but rather the build process, I am unclear as to what the legal requirement for including this in the source distribution. It would be nice if we had some clarity on the artifact. OTOH it is code under the ASL and the NOTICE.txt perhaps covers it. On 25 May 2013 13:51, Jason van Zyl ja...@tesla.io wrote: Here are the release bits for 3.1.0-alpha-1: Release notes: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=18967 Staging repository: https://repository.apache.org/content/repositories/maven-044/ Staged distribution:
Re: [VOTE] Apache 3.1.0-alpha-1
From my PoV the only outstanding issue is that the NOTICE.txt does not reflect the fact that it is now Eclipse Aether and no longer Sonatype Aether. I am unclear what the exact wording that is required, I am hoping that somebody else can correct the file. All the license header issues are, to my mind, fixed on master and Robert has switched over to package-info.java. I'll let Robert comment as to whether he sees the DOAP as a blocker. On 28 May 2013 22:08, Jason van Zyl ja...@tesla.io wrote: It's very easy to cut another release. If all the fixes are in that the PMC wishes it takes minutes to roll the release again. On May 28, 2013, at 4:43 PM, Robert Scholte rfscho...@apache.org wrote: Some additional remarks: - The copyright doesn't include current year (I've already fixed that on the trunk) - doap:generate fails: The generated DOAP doesn't respect ASF rules. Just to be sure I understand correctly: these alpha-versions will never be released. They are created so users can try them. -1 votes would mean it is not yet ready for a beta or final release. Is this right? Robert Op Tue, 28 May 2013 10:38:07 +0200 schreef Stephen Connolly stephen.alan.conno...@gmail.com: [x] Builds from source bundle [x] Builds some complex projects [x] Contains correct LICENSE.txt [ ] NOTICE.txt correctly attributes 3rd party components (See observation 1) [?] All source files, where appropriate, contain the ASL header (See observation 2) [?] Binary archives bundled within the source distribution (See observation 3) On the basis of the NOTICE.txt not acknowledging Eclipse Aether, and only on that basis I will be voting -0.9 (binding) The other issues are non-critical but it would be nice to tidy them up... nice to have. Observations 1. No attribution of Eclipse Aether, only referenced as developed by Sonatype. 2. The following 39 files are missing license headers: apache-maven/src/bin/m2.conf apache-maven/src/conf/logging/simplelogger.properties maven-aether-provider/src/main/java/org/apache/maven/repository/internal/package.html maven-aether-provider/src/site/apt/index.apt maven-artifact/src/site/apt/index.apt maven-compat/compatibility.cfl maven-compat/src/main/resources/META-INF/maven/plugin.xml maven-core/lifecycle-executor.txt maven-core/plugin-manager.txt maven-core/project-builder.txt maven-core/src/main/resources/org/apache/maven/messages/build.properties maven-core/src/site/apt/artifact-handlers.apt maven-core/src/site/apt/configuration-management.apt maven-core/src/site/apt/default-bindings.apt.vm maven-core/src/site/apt/getting-to-container-configured-mojos.apt maven-core/src/site/apt/index.apt maven-core/src/site/apt/inheritance.apt maven-core/src/site/apt/lifecycles.apt.vm maven-core/src/site/apt/offline-mode.apt maven-core/src/site/apt/plugin-execution-isolation.apt maven-core/src/site/apt/scripting-support/marmalade-support.apt maven-core/src/site/resources/design/2.1-lifecycle-refactor.graffle maven-embedder/src/examples/simple-project/src/main/java/org/apache/maven/embedder/App.java maven-embedder/src/examples/simple-project/src/test/java/org/apache/maven/embedder/AppTest.java maven-embedder/src/main/resources/META-INF/MANIFEST.MF maven-embedder/src/main/resources/META-INF/maven/slf4j-configuration.properties maven-embedder/src/site/apt/cli.apt.vm maven-embedder/src/site/apt/index.apt.vm maven-embedder/src/site/apt/logging.apt maven-model-builder/src/site/apt/index.apt maven-model-builder/src/site/apt/super-pom.apt.vm maven-model/src/main/java/org/apache/maven/model/io/xpp3/package.html maven-model/src/main/java/org/apache/maven/model/merge/package.html maven-model/src/main/java/org/apache/maven/model/package.html maven-model/src/site/apt/index.apt maven-plugin-api/src/site/apt/index.apt maven-repository-metadata/src/site/apt/index.apt maven-settings/src/site/apt/index.apt README.bootstrap.txt None of these are actual production code, so I don't see this as a blocker for release, but it would be good to tidy them up. Additionally, the embedder examples should have their license explicitly stated to remove confusion for anyone pegging the examples to build their own code upon. In addition I note that there are 432 test resources that do not have a license header, however, as test resources it is legitimate to argue that the license header could affect the test. It would be good if we could get that number reduced, but only if we are confident that we are not introducing false test passes in the process. 3. There is one (non-test) archive bundled within the distribution: maven-ant-tasks-2.1.1.jar Given that this specific artifact suffers from the bootstrap issue (i.e. it needs Maven to build it) and the source is available and this artifact is not part of
Re: [VOTE] Apache 3.1.0-alpha-1
This should suffice for the notice: https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commitdiff;h=b0a83f62 On May 28, 2013, at 5:48 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: From my PoV the only outstanding issue is that the NOTICE.txt does not reflect the fact that it is now Eclipse Aether and no longer Sonatype Aether. I am unclear what the exact wording that is required, I am hoping that somebody else can correct the file. All the license header issues are, to my mind, fixed on master and Robert has switched over to package-info.java. I'll let Robert comment as to whether he sees the DOAP as a blocker. On 28 May 2013 22:08, Jason van Zyl ja...@tesla.io wrote: It's very easy to cut another release. If all the fixes are in that the PMC wishes it takes minutes to roll the release again. On May 28, 2013, at 4:43 PM, Robert Scholte rfscho...@apache.org wrote: Some additional remarks: - The copyright doesn't include current year (I've already fixed that on the trunk) - doap:generate fails: The generated DOAP doesn't respect ASF rules. Just to be sure I understand correctly: these alpha-versions will never be released. They are created so users can try them. -1 votes would mean it is not yet ready for a beta or final release. Is this right? Robert Op Tue, 28 May 2013 10:38:07 +0200 schreef Stephen Connolly stephen.alan.conno...@gmail.com: [x] Builds from source bundle [x] Builds some complex projects [x] Contains correct LICENSE.txt [ ] NOTICE.txt correctly attributes 3rd party components (See observation 1) [?] All source files, where appropriate, contain the ASL header (See observation 2) [?] Binary archives bundled within the source distribution (See observation 3) On the basis of the NOTICE.txt not acknowledging Eclipse Aether, and only on that basis I will be voting -0.9 (binding) The other issues are non-critical but it would be nice to tidy them up... nice to have. Observations 1. No attribution of Eclipse Aether, only referenced as developed by Sonatype. 2. The following 39 files are missing license headers: apache-maven/src/bin/m2.conf apache-maven/src/conf/logging/simplelogger.properties maven-aether-provider/src/main/java/org/apache/maven/repository/internal/package.html maven-aether-provider/src/site/apt/index.apt maven-artifact/src/site/apt/index.apt maven-compat/compatibility.cfl maven-compat/src/main/resources/META-INF/maven/plugin.xml maven-core/lifecycle-executor.txt maven-core/plugin-manager.txt maven-core/project-builder.txt maven-core/src/main/resources/org/apache/maven/messages/build.properties maven-core/src/site/apt/artifact-handlers.apt maven-core/src/site/apt/configuration-management.apt maven-core/src/site/apt/default-bindings.apt.vm maven-core/src/site/apt/getting-to-container-configured-mojos.apt maven-core/src/site/apt/index.apt maven-core/src/site/apt/inheritance.apt maven-core/src/site/apt/lifecycles.apt.vm maven-core/src/site/apt/offline-mode.apt maven-core/src/site/apt/plugin-execution-isolation.apt maven-core/src/site/apt/scripting-support/marmalade-support.apt maven-core/src/site/resources/design/2.1-lifecycle-refactor.graffle maven-embedder/src/examples/simple-project/src/main/java/org/apache/maven/embedder/App.java maven-embedder/src/examples/simple-project/src/test/java/org/apache/maven/embedder/AppTest.java maven-embedder/src/main/resources/META-INF/MANIFEST.MF maven-embedder/src/main/resources/META-INF/maven/slf4j-configuration.properties maven-embedder/src/site/apt/cli.apt.vm maven-embedder/src/site/apt/index.apt.vm maven-embedder/src/site/apt/logging.apt maven-model-builder/src/site/apt/index.apt maven-model-builder/src/site/apt/super-pom.apt.vm maven-model/src/main/java/org/apache/maven/model/io/xpp3/package.html maven-model/src/main/java/org/apache/maven/model/merge/package.html maven-model/src/main/java/org/apache/maven/model/package.html maven-model/src/site/apt/index.apt maven-plugin-api/src/site/apt/index.apt maven-repository-metadata/src/site/apt/index.apt maven-settings/src/site/apt/index.apt README.bootstrap.txt None of these are actual production code, so I don't see this as a blocker for release, but it would be good to tidy them up. Additionally, the embedder examples should have their license explicitly stated to remove confusion for anyone pegging the examples to build their own code upon. In addition I note that there are 432 test resources that do not have a license header, however, as test resources it is legitimate to argue that the license header could affect the test. It would be good if we could get that number reduced, but only if we are confident that we are not introducing false test passes in the process. 3. There is one (non-test) archive bundled within the distribution: maven-ant-tasks-2.1.1.jar Given that this specific artifact suffers from the
Re: [VOTE] Apache 3.1.0-alpha-1
Yep looks fine to me. If you want to respin now, from _my_ PoV *should* be no issues now... of course who knows what will crop up with the next review ;-) On 29 May 2013 00:07, Jason van Zyl ja...@tesla.io wrote: This should suffice for the notice: https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commitdiff;h=b0a83f62 On May 28, 2013, at 5:48 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: From my PoV the only outstanding issue is that the NOTICE.txt does not reflect the fact that it is now Eclipse Aether and no longer Sonatype Aether. I am unclear what the exact wording that is required, I am hoping that somebody else can correct the file. All the license header issues are, to my mind, fixed on master and Robert has switched over to package-info.java. I'll let Robert comment as to whether he sees the DOAP as a blocker. On 28 May 2013 22:08, Jason van Zyl ja...@tesla.io wrote: It's very easy to cut another release. If all the fixes are in that the PMC wishes it takes minutes to roll the release again. On May 28, 2013, at 4:43 PM, Robert Scholte rfscho...@apache.org wrote: Some additional remarks: - The copyright doesn't include current year (I've already fixed that on the trunk) - doap:generate fails: The generated DOAP doesn't respect ASF rules. Just to be sure I understand correctly: these alpha-versions will never be released. They are created so users can try them. -1 votes would mean it is not yet ready for a beta or final release. Is this right? Robert Op Tue, 28 May 2013 10:38:07 +0200 schreef Stephen Connolly stephen.alan.conno...@gmail.com: [x] Builds from source bundle [x] Builds some complex projects [x] Contains correct LICENSE.txt [ ] NOTICE.txt correctly attributes 3rd party components (See observation 1) [?] All source files, where appropriate, contain the ASL header (See observation 2) [?] Binary archives bundled within the source distribution (See observation 3) On the basis of the NOTICE.txt not acknowledging Eclipse Aether, and only on that basis I will be voting -0.9 (binding) The other issues are non-critical but it would be nice to tidy them up... nice to have. Observations 1. No attribution of Eclipse Aether, only referenced as developed by Sonatype. 2. The following 39 files are missing license headers: apache-maven/src/bin/m2.conf apache-maven/src/conf/logging/simplelogger.properties maven-aether-provider/src/main/java/org/apache/maven/repository/internal/package.html maven-aether-provider/src/site/apt/index.apt maven-artifact/src/site/apt/index.apt maven-compat/compatibility.cfl maven-compat/src/main/resources/META-INF/maven/plugin.xml maven-core/lifecycle-executor.txt maven-core/plugin-manager.txt maven-core/project-builder.txt maven-core/src/main/resources/org/apache/maven/messages/build.properties maven-core/src/site/apt/artifact-handlers.apt maven-core/src/site/apt/configuration-management.apt maven-core/src/site/apt/default-bindings.apt.vm maven-core/src/site/apt/getting-to-container-configured-mojos.apt maven-core/src/site/apt/index.apt maven-core/src/site/apt/inheritance.apt maven-core/src/site/apt/lifecycles.apt.vm maven-core/src/site/apt/offline-mode.apt maven-core/src/site/apt/plugin-execution-isolation.apt maven-core/src/site/apt/scripting-support/marmalade-support.apt maven-core/src/site/resources/design/2.1-lifecycle-refactor.graffle maven-embedder/src/examples/simple-project/src/main/java/org/apache/maven/embedder/App.java maven-embedder/src/examples/simple-project/src/test/java/org/apache/maven/embedder/AppTest.java maven-embedder/src/main/resources/META-INF/MANIFEST.MF maven-embedder/src/main/resources/META-INF/maven/slf4j-configuration.properties maven-embedder/src/site/apt/cli.apt.vm maven-embedder/src/site/apt/index.apt.vm maven-embedder/src/site/apt/logging.apt maven-model-builder/src/site/apt/index.apt maven-model-builder/src/site/apt/super-pom.apt.vm maven-model/src/main/java/org/apache/maven/model/io/xpp3/package.html maven-model/src/main/java/org/apache/maven/model/merge/package.html maven-model/src/main/java/org/apache/maven/model/package.html maven-model/src/site/apt/index.apt maven-plugin-api/src/site/apt/index.apt maven-repository-metadata/src/site/apt/index.apt maven-settings/src/site/apt/index.apt README.bootstrap.txt None of these are actual production code, so I don't see this as a blocker for release, but it would be good to tidy them up. Additionally, the embedder examples should have their license explicitly stated to remove confusion for anyone pegging the examples to build their own code upon. In addition I note that there are 432 test resources that do not have a license header, however, as test resources it is legitimate to argue that the license header could
Re: [VOTE] Apache 3.1.0-alpha-1
I'll see if Robert wants to fix the DOAP file and I'll respin tomorrow after he's commented. On May 28, 2013, at 7:17 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: Yep looks fine to me. If you want to respin now, from _my_ PoV *should* be no issues now... of course who knows what will crop up with the next review ;-) On 29 May 2013 00:07, Jason van Zyl ja...@tesla.io wrote: This should suffice for the notice: https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commitdiff;h=b0a83f62 On May 28, 2013, at 5:48 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: From my PoV the only outstanding issue is that the NOTICE.txt does not reflect the fact that it is now Eclipse Aether and no longer Sonatype Aether. I am unclear what the exact wording that is required, I am hoping that somebody else can correct the file. All the license header issues are, to my mind, fixed on master and Robert has switched over to package-info.java. I'll let Robert comment as to whether he sees the DOAP as a blocker. On 28 May 2013 22:08, Jason van Zyl ja...@tesla.io wrote: It's very easy to cut another release. If all the fixes are in that the PMC wishes it takes minutes to roll the release again. On May 28, 2013, at 4:43 PM, Robert Scholte rfscho...@apache.org wrote: Some additional remarks: - The copyright doesn't include current year (I've already fixed that on the trunk) - doap:generate fails: The generated DOAP doesn't respect ASF rules. Just to be sure I understand correctly: these alpha-versions will never be released. They are created so users can try them. -1 votes would mean it is not yet ready for a beta or final release. Is this right? Robert Op Tue, 28 May 2013 10:38:07 +0200 schreef Stephen Connolly stephen.alan.conno...@gmail.com: [x] Builds from source bundle [x] Builds some complex projects [x] Contains correct LICENSE.txt [ ] NOTICE.txt correctly attributes 3rd party components (See observation 1) [?] All source files, where appropriate, contain the ASL header (See observation 2) [?] Binary archives bundled within the source distribution (See observation 3) On the basis of the NOTICE.txt not acknowledging Eclipse Aether, and only on that basis I will be voting -0.9 (binding) The other issues are non-critical but it would be nice to tidy them up... nice to have. Observations 1. No attribution of Eclipse Aether, only referenced as developed by Sonatype. 2. The following 39 files are missing license headers: apache-maven/src/bin/m2.conf apache-maven/src/conf/logging/simplelogger.properties maven-aether-provider/src/main/java/org/apache/maven/repository/internal/package.html maven-aether-provider/src/site/apt/index.apt maven-artifact/src/site/apt/index.apt maven-compat/compatibility.cfl maven-compat/src/main/resources/META-INF/maven/plugin.xml maven-core/lifecycle-executor.txt maven-core/plugin-manager.txt maven-core/project-builder.txt maven-core/src/main/resources/org/apache/maven/messages/build.properties maven-core/src/site/apt/artifact-handlers.apt maven-core/src/site/apt/configuration-management.apt maven-core/src/site/apt/default-bindings.apt.vm maven-core/src/site/apt/getting-to-container-configured-mojos.apt maven-core/src/site/apt/index.apt maven-core/src/site/apt/inheritance.apt maven-core/src/site/apt/lifecycles.apt.vm maven-core/src/site/apt/offline-mode.apt maven-core/src/site/apt/plugin-execution-isolation.apt maven-core/src/site/apt/scripting-support/marmalade-support.apt maven-core/src/site/resources/design/2.1-lifecycle-refactor.graffle maven-embedder/src/examples/simple-project/src/main/java/org/apache/maven/embedder/App.java maven-embedder/src/examples/simple-project/src/test/java/org/apache/maven/embedder/AppTest.java maven-embedder/src/main/resources/META-INF/MANIFEST.MF maven-embedder/src/main/resources/META-INF/maven/slf4j-configuration.properties maven-embedder/src/site/apt/cli.apt.vm maven-embedder/src/site/apt/index.apt.vm maven-embedder/src/site/apt/logging.apt maven-model-builder/src/site/apt/index.apt maven-model-builder/src/site/apt/super-pom.apt.vm maven-model/src/main/java/org/apache/maven/model/io/xpp3/package.html maven-model/src/main/java/org/apache/maven/model/merge/package.html maven-model/src/main/java/org/apache/maven/model/package.html maven-model/src/site/apt/index.apt maven-plugin-api/src/site/apt/index.apt maven-repository-metadata/src/site/apt/index.apt maven-settings/src/site/apt/index.apt README.bootstrap.txt None of these are actual production code, so I don't see this as a blocker for release, but it would be good to tidy them up. Additionally, the embedder examples should have their license explicitly stated to remove confusion for anyone pegging the examples to build their own code upon. In addition I note that there are 432 test resources that do not have
Re: [VOTE] Apache 3.1.0-alpha-1
OK. You should probably send out a Cancel notice for this vote and when launching the take 4 (I think this will be take 4 but I could be wrong) vote I recommend putting take 4 in the subject line as Gmail folded the -044 staging repo into the same thread as -038 so it was harder for some people to realize that there was a take 3 vote in play On 29 May 2013 00:21, Jason van Zyl ja...@tesla.io wrote: I'll see if Robert wants to fix the DOAP file and I'll respin tomorrow after he's commented. On May 28, 2013, at 7:17 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: Yep looks fine to me. If you want to respin now, from _my_ PoV *should* be no issues now... of course who knows what will crop up with the next review ;-) On 29 May 2013 00:07, Jason van Zyl ja...@tesla.io wrote: This should suffice for the notice: https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commitdiff;h=b0a83f62 On May 28, 2013, at 5:48 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: From my PoV the only outstanding issue is that the NOTICE.txt does not reflect the fact that it is now Eclipse Aether and no longer Sonatype Aether. I am unclear what the exact wording that is required, I am hoping that somebody else can correct the file. All the license header issues are, to my mind, fixed on master and Robert has switched over to package-info.java. I'll let Robert comment as to whether he sees the DOAP as a blocker. On 28 May 2013 22:08, Jason van Zyl ja...@tesla.io wrote: It's very easy to cut another release. If all the fixes are in that the PMC wishes it takes minutes to roll the release again. On May 28, 2013, at 4:43 PM, Robert Scholte rfscho...@apache.org wrote: Some additional remarks: - The copyright doesn't include current year (I've already fixed that on the trunk) - doap:generate fails: The generated DOAP doesn't respect ASF rules. Just to be sure I understand correctly: these alpha-versions will never be released. They are created so users can try them. -1 votes would mean it is not yet ready for a beta or final release. Is this right? Robert Op Tue, 28 May 2013 10:38:07 +0200 schreef Stephen Connolly stephen.alan.conno...@gmail.com: [x] Builds from source bundle [x] Builds some complex projects [x] Contains correct LICENSE.txt [ ] NOTICE.txt correctly attributes 3rd party components (See observation 1) [?] All source files, where appropriate, contain the ASL header (See observation 2) [?] Binary archives bundled within the source distribution (See observation 3) On the basis of the NOTICE.txt not acknowledging Eclipse Aether, and only on that basis I will be voting -0.9 (binding) The other issues are non-critical but it would be nice to tidy them up... nice to have. Observations 1. No attribution of Eclipse Aether, only referenced as developed by Sonatype. 2. The following 39 files are missing license headers: apache-maven/src/bin/m2.conf apache-maven/src/conf/logging/simplelogger.properties maven-aether-provider/src/main/java/org/apache/maven/repository/internal/package.html maven-aether-provider/src/site/apt/index.apt maven-artifact/src/site/apt/index.apt maven-compat/compatibility.cfl maven-compat/src/main/resources/META-INF/maven/plugin.xml maven-core/lifecycle-executor.txt maven-core/plugin-manager.txt maven-core/project-builder.txt maven-core/src/main/resources/org/apache/maven/messages/build.properties maven-core/src/site/apt/artifact-handlers.apt maven-core/src/site/apt/configuration-management.apt maven-core/src/site/apt/default-bindings.apt.vm maven-core/src/site/apt/getting-to-container-configured-mojos.apt maven-core/src/site/apt/index.apt maven-core/src/site/apt/inheritance.apt maven-core/src/site/apt/lifecycles.apt.vm maven-core/src/site/apt/offline-mode.apt maven-core/src/site/apt/plugin-execution-isolation.apt maven-core/src/site/apt/scripting-support/marmalade-support.apt maven-core/src/site/resources/design/2.1-lifecycle-refactor.graffle maven-embedder/src/examples/simple-project/src/main/java/org/apache/maven/embedder/App.java maven-embedder/src/examples/simple-project/src/test/java/org/apache/maven/embedder/AppTest.java maven-embedder/src/main/resources/META-INF/MANIFEST.MF maven-embedder/src/main/resources/META-INF/maven/slf4j-configuration.properties maven-embedder/src/site/apt/cli.apt.vm maven-embedder/src/site/apt/index.apt.vm maven-embedder/src/site/apt/logging.apt maven-model-builder/src/site/apt/index.apt maven-model-builder/src/site/apt/super-pom.apt.vm maven-model/src/main/java/org/apache/maven/model/io/xpp3/package.html maven-model/src/main/java/org/apache/maven/model/merge/package.html maven-model/src/main/java/org/apache/maven/model/package.html maven-model/src/site/apt/index.apt
CANCELLED Re: [VOTE] Apache 3.1.0-alpha-1
I'll respin in the morning with an identifying subject line. On May 28, 2013, at 7:27 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: OK. You should probably send out a Cancel notice for this vote and when launching the take 4 (I think this will be take 4 but I could be wrong) vote I recommend putting take 4 in the subject line as Gmail folded the -044 staging repo into the same thread as -038 so it was harder for some people to realize that there was a take 3 vote in play On 29 May 2013 00:21, Jason van Zyl ja...@tesla.io wrote: I'll see if Robert wants to fix the DOAP file and I'll respin tomorrow after he's commented. On May 28, 2013, at 7:17 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: Yep looks fine to me. If you want to respin now, from _my_ PoV *should* be no issues now... of course who knows what will crop up with the next review ;-) On 29 May 2013 00:07, Jason van Zyl ja...@tesla.io wrote: This should suffice for the notice: https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commitdiff;h=b0a83f62 On May 28, 2013, at 5:48 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: From my PoV the only outstanding issue is that the NOTICE.txt does not reflect the fact that it is now Eclipse Aether and no longer Sonatype Aether. I am unclear what the exact wording that is required, I am hoping that somebody else can correct the file. All the license header issues are, to my mind, fixed on master and Robert has switched over to package-info.java. I'll let Robert comment as to whether he sees the DOAP as a blocker. On 28 May 2013 22:08, Jason van Zyl ja...@tesla.io wrote: It's very easy to cut another release. If all the fixes are in that the PMC wishes it takes minutes to roll the release again. On May 28, 2013, at 4:43 PM, Robert Scholte rfscho...@apache.org wrote: Some additional remarks: - The copyright doesn't include current year (I've already fixed that on the trunk) - doap:generate fails: The generated DOAP doesn't respect ASF rules. Just to be sure I understand correctly: these alpha-versions will never be released. They are created so users can try them. -1 votes would mean it is not yet ready for a beta or final release. Is this right? Robert Op Tue, 28 May 2013 10:38:07 +0200 schreef Stephen Connolly stephen.alan.conno...@gmail.com: [x] Builds from source bundle [x] Builds some complex projects [x] Contains correct LICENSE.txt [ ] NOTICE.txt correctly attributes 3rd party components (See observation 1) [?] All source files, where appropriate, contain the ASL header (See observation 2) [?] Binary archives bundled within the source distribution (See observation 3) On the basis of the NOTICE.txt not acknowledging Eclipse Aether, and only on that basis I will be voting -0.9 (binding) The other issues are non-critical but it would be nice to tidy them up... nice to have. Observations 1. No attribution of Eclipse Aether, only referenced as developed by Sonatype. 2. The following 39 files are missing license headers: apache-maven/src/bin/m2.conf apache-maven/src/conf/logging/simplelogger.properties maven-aether-provider/src/main/java/org/apache/maven/repository/internal/package.html maven-aether-provider/src/site/apt/index.apt maven-artifact/src/site/apt/index.apt maven-compat/compatibility.cfl maven-compat/src/main/resources/META-INF/maven/plugin.xml maven-core/lifecycle-executor.txt maven-core/plugin-manager.txt maven-core/project-builder.txt maven-core/src/main/resources/org/apache/maven/messages/build.properties maven-core/src/site/apt/artifact-handlers.apt maven-core/src/site/apt/configuration-management.apt maven-core/src/site/apt/default-bindings.apt.vm maven-core/src/site/apt/getting-to-container-configured-mojos.apt maven-core/src/site/apt/index.apt maven-core/src/site/apt/inheritance.apt maven-core/src/site/apt/lifecycles.apt.vm maven-core/src/site/apt/offline-mode.apt maven-core/src/site/apt/plugin-execution-isolation.apt maven-core/src/site/apt/scripting-support/marmalade-support.apt maven-core/src/site/resources/design/2.1-lifecycle-refactor.graffle maven-embedder/src/examples/simple-project/src/main/java/org/apache/maven/embedder/App.java maven-embedder/src/examples/simple-project/src/test/java/org/apache/maven/embedder/AppTest.java maven-embedder/src/main/resources/META-INF/MANIFEST.MF maven-embedder/src/main/resources/META-INF/maven/slf4j-configuration.properties maven-embedder/src/site/apt/cli.apt.vm maven-embedder/src/site/apt/index.apt.vm maven-embedder/src/site/apt/logging.apt maven-model-builder/src/site/apt/index.apt maven-model-builder/src/site/apt/super-pom.apt.vm maven-model/src/main/java/org/apache/maven/model/io/xpp3/package.html maven-model/src/main/java/org/apache/maven/model/merge/package.html
Re: [VOTE] Apache 3.1.0-alpha-1
Pushed a small additional fix for typo and clarification based on the names in the POMs. On 28/05/2013, at 4:07 PM, Jason van Zyl ja...@tesla.io wrote: This should suffice for the notice: https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commitdiff;h=b0a83f62 On May 28, 2013, at 5:48 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: From my PoV the only outstanding issue is that the NOTICE.txt does not reflect the fact that it is now Eclipse Aether and no longer Sonatype Aether. I am unclear what the exact wording that is required, I am hoping that somebody else can correct the file. All the license header issues are, to my mind, fixed on master and Robert has switched over to package-info.java. I'll let Robert comment as to whether he sees the DOAP as a blocker. On 28 May 2013 22:08, Jason van Zyl ja...@tesla.io wrote: It's very easy to cut another release. If all the fixes are in that the PMC wishes it takes minutes to roll the release again. On May 28, 2013, at 4:43 PM, Robert Scholte rfscho...@apache.org wrote: Some additional remarks: - The copyright doesn't include current year (I've already fixed that on the trunk) - doap:generate fails: The generated DOAP doesn't respect ASF rules. Just to be sure I understand correctly: these alpha-versions will never be released. They are created so users can try them. -1 votes would mean it is not yet ready for a beta or final release. Is this right? Robert Op Tue, 28 May 2013 10:38:07 +0200 schreef Stephen Connolly stephen.alan.conno...@gmail.com: [x] Builds from source bundle [x] Builds some complex projects [x] Contains correct LICENSE.txt [ ] NOTICE.txt correctly attributes 3rd party components (See observation 1) [?] All source files, where appropriate, contain the ASL header (See observation 2) [?] Binary archives bundled within the source distribution (See observation 3) On the basis of the NOTICE.txt not acknowledging Eclipse Aether, and only on that basis I will be voting -0.9 (binding) The other issues are non-critical but it would be nice to tidy them up... nice to have. Observations 1. No attribution of Eclipse Aether, only referenced as developed by Sonatype. 2. The following 39 files are missing license headers: apache-maven/src/bin/m2.conf apache-maven/src/conf/logging/simplelogger.properties maven-aether-provider/src/main/java/org/apache/maven/repository/internal/package.html maven-aether-provider/src/site/apt/index.apt maven-artifact/src/site/apt/index.apt maven-compat/compatibility.cfl maven-compat/src/main/resources/META-INF/maven/plugin.xml maven-core/lifecycle-executor.txt maven-core/plugin-manager.txt maven-core/project-builder.txt maven-core/src/main/resources/org/apache/maven/messages/build.properties maven-core/src/site/apt/artifact-handlers.apt maven-core/src/site/apt/configuration-management.apt maven-core/src/site/apt/default-bindings.apt.vm maven-core/src/site/apt/getting-to-container-configured-mojos.apt maven-core/src/site/apt/index.apt maven-core/src/site/apt/inheritance.apt maven-core/src/site/apt/lifecycles.apt.vm maven-core/src/site/apt/offline-mode.apt maven-core/src/site/apt/plugin-execution-isolation.apt maven-core/src/site/apt/scripting-support/marmalade-support.apt maven-core/src/site/resources/design/2.1-lifecycle-refactor.graffle maven-embedder/src/examples/simple-project/src/main/java/org/apache/maven/embedder/App.java maven-embedder/src/examples/simple-project/src/test/java/org/apache/maven/embedder/AppTest.java maven-embedder/src/main/resources/META-INF/MANIFEST.MF maven-embedder/src/main/resources/META-INF/maven/slf4j-configuration.properties maven-embedder/src/site/apt/cli.apt.vm maven-embedder/src/site/apt/index.apt.vm maven-embedder/src/site/apt/logging.apt maven-model-builder/src/site/apt/index.apt maven-model-builder/src/site/apt/super-pom.apt.vm maven-model/src/main/java/org/apache/maven/model/io/xpp3/package.html maven-model/src/main/java/org/apache/maven/model/merge/package.html maven-model/src/main/java/org/apache/maven/model/package.html maven-model/src/site/apt/index.apt maven-plugin-api/src/site/apt/index.apt maven-repository-metadata/src/site/apt/index.apt maven-settings/src/site/apt/index.apt README.bootstrap.txt None of these are actual production code, so I don't see this as a blocker for release, but it would be good to tidy them up. Additionally, the embedder examples should have their license explicitly stated to remove confusion for anyone pegging the examples to build their own code upon. In addition I note that there are 432 test resources that do not have a license header, however, as test resources it is legitimate to argue that the license header could affect the test. It would be good if we could get that number reduced, but only if we are confident that we are not introducing false test passes in the process.
Re: [VOTE] Apache 3.1.0-alpha-1
I'd like to work on Arnaud's idea of error message enhancement in case a plugin fails because of unavailable Sonatype Aether: if you can let me 12 more hours from now, I'll do it tonight Regards, Hervé Le mardi 28 mai 2013 19:21:52 Jason van Zyl a écrit : I'll see if Robert wants to fix the DOAP file and I'll respin tomorrow after he's commented. On May 28, 2013, at 7:17 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: Yep looks fine to me. If you want to respin now, from _my_ PoV *should* be no issues now... of course who knows what will crop up with the next review ;-) On 29 May 2013 00:07, Jason van Zyl ja...@tesla.io wrote: This should suffice for the notice: https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commitdiff;h=b0a83f 62 On May 28, 2013, at 5:48 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: From my PoV the only outstanding issue is that the NOTICE.txt does not reflect the fact that it is now Eclipse Aether and no longer Sonatype Aether. I am unclear what the exact wording that is required, I am hoping that somebody else can correct the file. All the license header issues are, to my mind, fixed on master and Robert has switched over to package-info.java. I'll let Robert comment as to whether he sees the DOAP as a blocker. On 28 May 2013 22:08, Jason van Zyl ja...@tesla.io wrote: It's very easy to cut another release. If all the fixes are in that the PMC wishes it takes minutes to roll the release again. On May 28, 2013, at 4:43 PM, Robert Scholte rfscho...@apache.org wrote: Some additional remarks: - The copyright doesn't include current year (I've already fixed that on the trunk) - doap:generate fails: The generated DOAP doesn't respect ASF rules. Just to be sure I understand correctly: these alpha-versions will never be released. They are created so users can try them. -1 votes would mean it is not yet ready for a beta or final release. Is this right? Robert Op Tue, 28 May 2013 10:38:07 +0200 schreef Stephen Connolly stephen.alan.conno...@gmail.com: [x] Builds from source bundle [x] Builds some complex projects [x] Contains correct LICENSE.txt [ ] NOTICE.txt correctly attributes 3rd party components (See observation 1) [?] All source files, where appropriate, contain the ASL header (See observation 2) [?] Binary archives bundled within the source distribution (See observation 3) On the basis of the NOTICE.txt not acknowledging Eclipse Aether, and only on that basis I will be voting -0.9 (binding) The other issues are non-critical but it would be nice to tidy them up... nice to have. Observations 1. No attribution of Eclipse Aether, only referenced as developed by Sonatype. 2. The following 39 files are missing license headers: apache-maven/src/bin/m2.conf apache-maven/src/conf/logging/simplelogger.properties maven-aether-provider/src/main/java/org/apache/maven/repository/internal/ package.html maven-aether-provider/src/site/apt/index.apt maven-artifact/src/site/apt/index.apt maven-compat/compatibility.cfl maven-compat/src/main/resources/META-INF/maven/plugin.xml maven-core/lifecycle-executor.txt maven-core/plugin-manager.txt maven-core/project-builder.txt maven-core/src/main/resources/org/apache/maven/messages/build.propertie s maven-core/src/site/apt/artifact-handlers.apt maven-core/src/site/apt/configuration-management.apt maven-core/src/site/apt/default-bindings.apt.vm maven-core/src/site/apt/getting-to-container-configured-mojos.apt maven-core/src/site/apt/index.apt maven-core/src/site/apt/inheritance.apt maven-core/src/site/apt/lifecycles.apt.vm maven-core/src/site/apt/offline-mode.apt maven-core/src/site/apt/plugin-execution-isolation.apt maven-core/src/site/apt/scripting-support/marmalade-support.apt maven-core/src/site/resources/design/2.1-lifecycle-refactor.graffle maven-embedder/src/examples/simple-project/src/main/java/org/apache/maven /embedder/App.java maven-embedder/src/examples/simple-project/src/test/java/org/apache/maven /embedder/AppTest.java maven-embedder/src/main/resources/META-INF/MANIFEST.MF maven-embedder/src/main/resources/META-INF/maven/slf4j-configuration.prop erties maven-embedder/src/site/apt/cli.apt.vm maven-embedder/src/site/apt/index.apt.vm maven-embedder/src/site/apt/logging.apt maven-model-builder/src/site/apt/index.apt maven-model-builder/src/site/apt/super-pom.apt.vm maven-model/src/main/java/org/apache/maven/model/io/xpp3/package.html maven-model/src/main/java/org/apache/maven/model/merge/package.html maven-model/src/main/java/org/apache/maven/model/package.html maven-model/src/site/apt/index.apt maven-plugin-api/src/site/apt/index.apt
Re: [VOTE] Apache 3.1.0-alpha-1
good idea: can you open a Jira issue? notice, at a first pass, improving content of http://cwiki.apache.org/confluence/display/MAVEN/PluginContainerException to explain the special case of Aether is easy. But I'll try to have a dedicated link tonight: I know that the code will go in DefaultExceptionHandler class in maven-core, my only hesitation actually is how to code ITs to test the result: are there already ITs checking such error messages? Regards, Hervé Le mardi 28 mai 2013 18:31:26 Arnaud Héritier a écrit : For now I had no issue with this release after an upgrade of few plugins In the future (another Alpha ..) couldn't you catch such error and provide a more user friendly message asking to upgrade the plugin : [INFO] Dependency-reduced POM written at: /Users/arnaud/Code/eXo/platform-public-distributions/plf-tomcat-extensions-m anager/dependency-reduced-pom.xml [WARNING] Error injecting: org.apache.maven.shared.dependency.graph.internal.Maven3DependencyGraphBuild er java.lang.NoClassDefFoundError: org/sonatype/aether/graph/Dependency at java.lang.Class.getDeclaredMethods0(Native Method) at java.lang.Class.privateGetDeclaredMethods(Class.java:2436) at java.lang.Class.getDeclaredMethods(Class.java:1793) at com.google.inject.spi.InjectionPoint.getInjectionPoints(InjectionPoint.java: 674) at com.google.inject.spi.InjectionPoint.forInstanceMethodsAndFields(InjectionPo int.java:366) at com.google.inject.internal.ConstructorBindingImpl.getInternalDependencies(Co nstructorBindingImpl.java:165) at com.google.inject.internal.InjectorImpl.getInternalDependencies(InjectorImpl .java:609) at com.google.inject.internal.InjectorImpl.cleanup(InjectorImpl.java:565) at com.google.inject.internal.InjectorImpl.initializeJitBinding(InjectorImpl.ja va:551) at com.google.inject.internal.InjectorImpl.createJustInTimeBinding(InjectorImpl .java:865) at com.google.inject.internal.InjectorImpl.createJustInTimeBindingRecursive(Inj ectorImpl.java:790) at com.google.inject.internal.InjectorImpl.getJustInTimeBinding(InjectorImpl.ja va:278) at com.google.inject.internal.InjectorImpl.getBindingOrThrow(InjectorImpl.java: 210) at com.google.inject.internal.InjectorImpl.getProviderOrThrow(InjectorImpl.java :986) at com.google.inject.internal.InjectorImpl.getProvider(InjectorImpl.java:1019) at com.google.inject.internal.InjectorImpl.getProvider(InjectorImpl.java:982) at com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:1032) at org.eclipse.sisu.reflect.AbstractDeferredClass.get(AbstractDeferredClass.jav a:44) at com.google.inject.internal.ProviderInternalFactory.provision(ProviderInterna lFactory.java:86) at com.google.inject.internal.InternalFactoryToInitializableAdapter.provision(I nternalFactoryToInitializableAdapter.java:55) at com.google.inject.internal.ProviderInternalFactory$1.call(ProviderInternalFa ctory.java:70) at com.google.inject.internal.ProvisionListenerStackCallback$Provision.provisio n(ProvisionListenerStackCallback.java:100) at org.eclipse.sisu.plexus.lifecycles.PlexusLifecycleManager.onProvision(Plexus LifecycleManager.java:134) at com.google.inject.internal.ProvisionListenerStackCallback$Provision.provisio n(ProvisionListenerStackCallback.java:109) at com.google.inject.internal.ProvisionListenerStackCallback.provision(Provisio nListenerStackCallback.java:55) at com.google.inject.internal.ProviderInternalFactory.circularGet(ProviderInter nalFactory.java:68) at com.google.inject.internal.InternalFactoryToInitializableAdapter.get(Interna lFactoryToInitializableAdapter.java:47) at com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderT oInternalFactoryAdapter.java:46) at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1054 ) at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToIn ternalFactoryAdapter.java:40) at com.google.inject.Scopes$1$1.get(Scopes.java:59) at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFact oryToProviderAdapter.java:41) at com.google.inject.internal.InjectorImpl$2$1.call(InjectorImpl.java:997) at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1047 ) at com.google.inject.internal.InjectorImpl$2.get(InjectorImpl.java:993) at org.eclipse.sisu.locators.LazyBeanEntry.getValue(LazyBeanEntry.java:82) at org.eclipse.sisu.plexus.locators.LazyPlexusBean.getValue(LazyPlexusBean.java :52) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.jav a:259) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.jav a:239) at org.apache.maven.shared.dependency.graph.internal.DefaultDependencyGraphBuil der.buildDependencyGraph(DefaultDependencyGraphBuilder.java:60) at org.apache.maven.plugins.shade.mojo.ShadeMojo.updateExcludesInDeps(ShadeMojo .java:965) at org.apache.maven.plugins.shade.mojo.ShadeMojo.createDependencyReducedPom(Sha
Re: [VOTE] Apache 3.1.0-alpha-1
Greetings, On Wed, May 29, 2013 at 1:36 AM, Hervé BOUTEMY herve.bout...@free.fr wrote: I'd like to work on Arnaud's idea of error message enhancement in case a plugin fails because of unavailable Sonatype Aether: if you can let me 12 more hours from now, I'll do it tonight Version numbers are cheap. Can't we just make an alpha-2? I'm just a user, but I'm getting pretty sick of staged alpha releases being dropped. This happened with 3.0.5 as well. Just release it already. They are alphas. Christ. -Jesse - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Apache 3.1.0-alpha-1
+1 works fine for me Regards, Hervé Le samedi 25 mai 2013 08:51:00 Jason van Zyl a écrit : Here are the release bits for 3.1.0-alpha-1: Release notes: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=18 967 Staging repository: https://repository.apache.org/content/repositories/maven-044/ Staged distribution: https://repository.apache.org/content/repositories/maven-044/org/apache/mave n/apache-maven/3.1.0-alpha-1/ Staged Site: http://maven.apache.org/ref/3.1.0-alpha-1 Thanks, Jason -- Jason van Zyl Founder CTO, Sonatype Founder, Apache Maven http://twitter.com/jvanzyl - We know what we are, but know not what we may be. -- Shakespeare - 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: [VOTE] Apache 3.1.0-alpha-1
I deployed Maven 3.1.0-alpha-1 site with itself :) Regards, Hervé Le samedi 25 mai 2013 17:30:50 Mark Derricutt a écrit : +1 Looking good for me on my multi-module OSGi builds, clojure-maven-plugin and ITs, releases made to both projects and so far nothing jumping out at me - tho I'm not building any maven sites or anything. Jason van Zyl wrote: Thanks. On May 23, 2013, at 6:40 PM, Hervé BOUTEMYherve.bout...@free.fr wrote: site published (sync pending): http://maven.apache.org/ref/3.1.0-alpha-1 Regards, Hervé Le jeudi 23 mai 2013 16:52:13 Jason van Zyl a écrit : If you are to test the source you're suppose to actually test the source distribution. If you want to test via the sha1 here you go: 32d720ea0c669d4f55c0f71e4f3e054695648732 If someone else can publish the site I'd appreciate it. On May 23, 2013, at 4:26 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: What is the tag or git hash (as votes are on source not on binary builds) and is the site staged? On Thursday, 23 May 2013, Jason van Zyl wrote: Here are the release bits for 3.1.0-alpha-1: Release notes: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500vers ion =18967 Staging repository: https://repository.apache.org/content/repositories/maven-038/ Staged distribution: https://repository.apache.org/content/repositories/maven-038/org/apach e/m aven/apache-maven/3.1.0-alpha-1/ Thanks, Jason -- Jason van Zyl Founder CTO, Sonatype Founder, Apache Maven http://twitter.com/jvanzyl - We know what we are, but know not what we may be. -- Shakespeare - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.orgjavascript:; For additional commands, e-mail: dev-h...@maven.apache.orgjavascript:; Thanks, Jason -- Jason van Zyl Founder CTO, Sonatype Founder, Apache Maven http://twitter.com/jvanzyl - A language that doesn’t affect the way you think about programming is not worth knowing. -- Alan Perlis - 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 - happiness is like a butterfly: the more you chase it, the more it will elude you, but if you turn your attention to other things, it will come and sit softly on your shoulder ... -- Thoreau - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Apache 3.1.0-alpha-1
the snapshot repository in parent pom is still here: IIUC, it was one of the reason you cancelled previous vote is this intentional? what impact does it have? Regards, Hervé Le jeudi 23 mai 2013 14:02:44 Jason van Zyl a écrit : Here are the release bits for 3.1.0-alpha-1: Release notes: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=18 967 Staging repository: https://repository.apache.org/content/repositories/maven-038/ Staged distribution: https://repository.apache.org/content/repositories/maven-038/org/apache/mave n/apache-maven/3.1.0-alpha-1/ Thanks, Jason -- Jason van Zyl Founder CTO, Sonatype Founder, Apache Maven http://twitter.com/jvanzyl - We know what we are, but know not what we may be. -- Shakespeare - 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: [VOTE] Apache 3.1.0-alpha-1
Well that's just showing off now isn't it :) Hervé BOUTEMY wrote: I deployed Maven 3.1.0-alpha-1 site with itself:) - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Apache 3.1.0-alpha-1
Not intentional, I'm working in a branch from the first time I cut the release and I changed that one. I'll re-cut it shortly. On May 25, 2013, at 3:25 AM, Hervé BOUTEMY herve.bout...@free.fr wrote: the snapshot repository in parent pom is still here: IIUC, it was one of the reason you cancelled previous vote is this intentional? what impact does it have? Regards, Hervé Le jeudi 23 mai 2013 14:02:44 Jason van Zyl a écrit : Here are the release bits for 3.1.0-alpha-1: Release notes: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=18 967 Staging repository: https://repository.apache.org/content/repositories/maven-038/ Staged distribution: https://repository.apache.org/content/repositories/maven-038/org/apache/mave n/apache-maven/3.1.0-alpha-1/ Thanks, Jason -- Jason van Zyl Founder CTO, Sonatype Founder, Apache Maven http://twitter.com/jvanzyl - We know what we are, but know not what we may be. -- Shakespeare - 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 - We know what we are, but know not what we may be. -- Shakespeare
CANCELLED Re: [VOTE] Apache 3.1.0-alpha-1
And one more time. The snapshot repository is still in there. On May 23, 2013, at 2:02 PM, Jason van Zyl ja...@tesla.io wrote: Here are the release bits for 3.1.0-alpha-1: Release notes: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=18967 Staging repository: https://repository.apache.org/content/repositories/maven-038/ Staged distribution: https://repository.apache.org/content/repositories/maven-038/org/apache/maven/apache-maven/3.1.0-alpha-1/ Thanks, Jason -- Jason van Zyl Founder CTO, Sonatype Founder, Apache Maven http://twitter.com/jvanzyl - We know what we are, but know not what we may be. -- Shakespeare - 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 - In short, man creates for himself a new religion of a rational and technical order to justify his work and to be justified in it. -- Jacques Ellul, The Technological Society
RE: [VOTE] Apache 3.1.0-alpha-1
+1 (not binding) only need a few artifact update for using 3.1.0-a1. I tested it on a win 8x64 box on new empty local repo. I use for apache archiva clean install + tomcat7 and site goals. -Need to update site plugin from 3.2 to 3.3. Avid user of nbm plugin wich is not compatible -Need to update dependency shared:maven-dependency-tree from 2.0 to 2.1 Regards, Eric -Message d'origine- De : Jason van Zyl [mailto:ja...@tesla.io] Envoyé : samedi 25 mai 2013 14:51 À : Maven Developers List Objet : [VOTE] Apache 3.1.0-alpha-1 Here are the release bits for 3.1.0-alpha-1: Release notes: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=18 967 Staging repository: https://repository.apache.org/content/repositories/maven-044/ Staged distribution: https://repository.apache.org/content/repositories/maven-044/org/apache/mave n/apache-maven/3.1.0-alpha-1/ Staged Site: http://maven.apache.org/ref/3.1.0-alpha-1 Thanks, Jason -- Jason van Zyl Founder CTO, Sonatype Founder, Apache Maven http://twitter.com/jvanzyl - We know what we are, but know not what we may be. -- Shakespeare - 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: [VOTE] Apache 3.1.0-alpha-1
+1 (non binding) as mentioned before, works without issue on several multi-module OSGi based artifacts, plus the clojure-maven-plugin and IT tests. Eric Barboni wrote: +1 (not binding) only need a few artifact update for using 3.1.0-a1. I tested it on a win 8x64 box on new empty local repo. I use for apache archiva clean install + tomcat7 and site goals. -Need to update site plugin from 3.2 to 3.3. Avid user of nbm plugin wich is not compatible -Need to update dependency shared:maven-dependency-tree from 2.0 to 2.1 Regards, Eric -Message d'origine- De : Jason van Zyl [mailto:ja...@tesla.io] Envoyé : samedi 25 mai 2013 14:51 À : Maven Developers List Objet : [VOTE] Apache 3.1.0-alpha-1 Here are the release bits for 3.1.0-alpha-1: Release notes: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=18 967 Staging repository: https://repository.apache.org/content/repositories/maven-044/ Staged distribution: https://repository.apache.org/content/repositories/maven-044/org/apache/mave n/apache-maven/3.1.0-alpha-1/ Staged Site: http://maven.apache.org/ref/3.1.0-alpha-1 Thanks, Jason -- Jason van Zyl Founder CTO, Sonatype Founder, Apache Maven http://twitter.com/jvanzyl - We know what we are, but know not what we may be. -- Shakespeare - 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: [VOTE] Apache 3.1.0-alpha-1
+1 Looking good for me on my multi-module OSGi builds, clojure-maven-plugin and ITs, releases made to both projects and so far nothing jumping out at me - tho I'm not building any maven sites or anything. Jason van Zyl wrote: Thanks. On May 23, 2013, at 6:40 PM, Hervé BOUTEMYherve.bout...@free.fr wrote: site published (sync pending): http://maven.apache.org/ref/3.1.0-alpha-1 Regards, Hervé Le jeudi 23 mai 2013 16:52:13 Jason van Zyl a écrit : If you are to test the source you're suppose to actually test the source distribution. If you want to test via the sha1 here you go: 32d720ea0c669d4f55c0f71e4f3e054695648732 If someone else can publish the site I'd appreciate it. On May 23, 2013, at 4:26 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: What is the tag or git hash (as votes are on source not on binary builds) and is the site staged? On Thursday, 23 May 2013, Jason van Zyl wrote: Here are the release bits for 3.1.0-alpha-1: Release notes: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version =18967 Staging repository: https://repository.apache.org/content/repositories/maven-038/ Staged distribution: https://repository.apache.org/content/repositories/maven-038/org/apache/m aven/apache-maven/3.1.0-alpha-1/ Thanks, Jason -- Jason van Zyl Founder CTO, Sonatype Founder, Apache Maven http://twitter.com/jvanzyl - We know what we are, but know not what we may be. -- Shakespeare - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.orgjavascript:; For additional commands, e-mail: dev-h...@maven.apache.orgjavascript:; Thanks, Jason -- Jason van Zyl Founder CTO, Sonatype Founder, Apache Maven http://twitter.com/jvanzyl - A language that doesn’t affect the way you think about programming is not worth knowing. -- Alan Perlis - 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 - happiness is like a butterfly: the more you chase it, the more it will elude you, but if you turn your attention to other things, it will come and sit softly on your shoulder ... -- Thoreau
Re: [VOTE] Apache 3.1.0-alpha-1
What is the tag or git hash (as votes are on source not on binary builds) and is the site staged? On Thursday, 23 May 2013, Jason van Zyl wrote: Here are the release bits for 3.1.0-alpha-1: Release notes: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=18967 Staging repository: https://repository.apache.org/content/repositories/maven-038/ Staged distribution: https://repository.apache.org/content/repositories/maven-038/org/apache/maven/apache-maven/3.1.0-alpha-1/ Thanks, Jason -- Jason van Zyl Founder CTO, Sonatype Founder, Apache Maven http://twitter.com/jvanzyl - We know what we are, but know not what we may be. -- Shakespeare - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org javascript:; For additional commands, e-mail: dev-h...@maven.apache.org javascript:; -- Sent from my phone
Re: [VOTE] Apache 3.1.0-alpha-1
If you are to test the source you're suppose to actually test the source distribution. If you want to test via the sha1 here you go: 32d720ea0c669d4f55c0f71e4f3e054695648732 If someone else can publish the site I'd appreciate it. On May 23, 2013, at 4:26 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: What is the tag or git hash (as votes are on source not on binary builds) and is the site staged? On Thursday, 23 May 2013, Jason van Zyl wrote: Here are the release bits for 3.1.0-alpha-1: Release notes: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=18967 Staging repository: https://repository.apache.org/content/repositories/maven-038/ Staged distribution: https://repository.apache.org/content/repositories/maven-038/org/apache/maven/apache-maven/3.1.0-alpha-1/ Thanks, Jason -- Jason van Zyl Founder CTO, Sonatype Founder, Apache Maven http://twitter.com/jvanzyl - We know what we are, but know not what we may be. -- Shakespeare - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org javascript:; For additional commands, e-mail: dev-h...@maven.apache.org javascript:; -- Sent from my phone Thanks, Jason -- Jason van Zyl Founder CTO, Sonatype Founder, Apache Maven http://twitter.com/jvanzyl - A language that doesn’t affect the way you think about programming is not worth knowing. -- Alan Perlis
Re: [VOTE] Apache 3.1.0-alpha-1
site published (sync pending): http://maven.apache.org/ref/3.1.0-alpha-1 Regards, Hervé Le jeudi 23 mai 2013 16:52:13 Jason van Zyl a écrit : If you are to test the source you're suppose to actually test the source distribution. If you want to test via the sha1 here you go: 32d720ea0c669d4f55c0f71e4f3e054695648732 If someone else can publish the site I'd appreciate it. On May 23, 2013, at 4:26 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: What is the tag or git hash (as votes are on source not on binary builds) and is the site staged? On Thursday, 23 May 2013, Jason van Zyl wrote: Here are the release bits for 3.1.0-alpha-1: Release notes: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version =18967 Staging repository: https://repository.apache.org/content/repositories/maven-038/ Staged distribution: https://repository.apache.org/content/repositories/maven-038/org/apache/m aven/apache-maven/3.1.0-alpha-1/ Thanks, Jason -- Jason van Zyl Founder CTO, Sonatype Founder, Apache Maven http://twitter.com/jvanzyl - We know what we are, but know not what we may be. -- Shakespeare - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org javascript:; For additional commands, e-mail: dev-h...@maven.apache.org javascript:; Thanks, Jason -- Jason van Zyl Founder CTO, Sonatype Founder, Apache Maven http://twitter.com/jvanzyl - A language that doesn’t affect the way you think about programming is not worth knowing. -- Alan Perlis - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Apache 3.1.0-alpha-1
Thanks. On May 23, 2013, at 6:40 PM, Hervé BOUTEMY herve.bout...@free.fr wrote: site published (sync pending): http://maven.apache.org/ref/3.1.0-alpha-1 Regards, Hervé Le jeudi 23 mai 2013 16:52:13 Jason van Zyl a écrit : If you are to test the source you're suppose to actually test the source distribution. If you want to test via the sha1 here you go: 32d720ea0c669d4f55c0f71e4f3e054695648732 If someone else can publish the site I'd appreciate it. On May 23, 2013, at 4:26 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: What is the tag or git hash (as votes are on source not on binary builds) and is the site staged? On Thursday, 23 May 2013, Jason van Zyl wrote: Here are the release bits for 3.1.0-alpha-1: Release notes: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version =18967 Staging repository: https://repository.apache.org/content/repositories/maven-038/ Staged distribution: https://repository.apache.org/content/repositories/maven-038/org/apache/m aven/apache-maven/3.1.0-alpha-1/ Thanks, Jason -- Jason van Zyl Founder CTO, Sonatype Founder, Apache Maven http://twitter.com/jvanzyl - We know what we are, but know not what we may be. -- Shakespeare - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org javascript:; For additional commands, e-mail: dev-h...@maven.apache.org javascript:; Thanks, Jason -- Jason van Zyl Founder CTO, Sonatype Founder, Apache Maven http://twitter.com/jvanzyl - A language that doesn’t affect the way you think about programming is not worth knowing. -- Alan Perlis - 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 - happiness is like a butterfly: the more you chase it, the more it will elude you, but if you turn your attention to other things, it will come and sit softly on your shoulder ... -- Thoreau
Re: [VOTE] Apache 3.1.0-alpha-1
The vote for 3.1.0-alpha-1 is cancelled. There is a snapshot repository in the parent POM and the vote has gone on for far longer than acceptable. Hervé go ahead and update any versions of the POMs you like, I have some small changes I'm going to make and when you're happy with the updated plugins I'll cut the release again. On May 4, 2013, at 11:40 AM, Jason van Zyl ja...@tesla.io wrote: Sure, update all the plugins. We might as well do all that maintenance work now before the next release. I can look at making an enforcer rule. It's been something I've been meaning at looking at is breaking out all the checks in the release plugin to enforcer rules so they can be used anywhere. Inside and outside the release plugin. On May 4, 2013, at 11:26 AM, Hervé BOUTEMY herve.bout...@free.fr wrote: uh, I didn't see this one :( if the check can be automated through an enforcer rule, this would be a Good Thing (TM) I finally found my way with maven-dependency-tree (vote in progress) + dependency:tree (re-added verbose mode, which was a big users expectation). And since I have some time this week (holidays), I should be able to release everything during these holidays. It would be nice to update default plugins in Maven core before the next release candidate. Regards, Hervé Le samedi 4 mai 2013 10:12:25 Jason van Zyl a écrit : I will cancel the vote and respin it. No one has looked that hard: there's a snapshot repository in the top-level POM. I haven't made any noise as Hervé is trying to release all the prerequisites so that some of the standard plugins don't fail. On May 2, 2013, at 5:16 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: Currently it's +1 (binding): Hervé me Some other +1's and -1's I'd expect the release manager for ths release to have made some noise by now (as any release manager should) On Thursday, 2 May 2013, Stephen Connolly wrote: I think we are just waiting for one more binding vote from a PMC member... But somebody should double check the count On Thursday, 2 May 2013, ceki wrote: Hello all, Out of curiosity, are there any other non-resolved issues holding up this release? Best regards, On 23.04.2013 12:24, Stephen Connolly wrote: +1 (binding) for 3.1.0-alpha-1 The following issue needs to be resolved before I will vote +1 on a non-alpha release: http://jira.codehaus.org/**browse/MNG-5470http://jira.codehaus.org/brows e/MNG-5470 RAT is reporting the 391 files are either missing license headers or have not been flagged as files that cannot support a license header. Most of these are test data files and I would be happy to argue that the test may require a specific exact content for reproducibility, but the following I do not feel I can make a case for. I will require these 39 files to be addressed in some way before the final 3.1.0 release or I cannot provide a binding vote for the release. (the MANIFEST.MF may be one where a header does not make sense, but it is a non-generated file) I cannot speak for the rest of the PMC, but my understanding is that as a PMC member it is one of our duties to ensure that the source (which is what the vote is on) has met with the ASF requirements for license headers. * Unapproved licenses: apache-maven/src/bin/m2.conf apache-maven/src/conf/logging/**simplelogger.properties maven-aether-provider/src/**main/java/org/apache/maven/** repository/internal/package.**html maven-aether-provider/src/**site/apt/index.apt maven-artifact/src/site/apt/**index.apt maven-compat/compatibility.cfl maven-compat/src/main/**resources/META-INF/maven/**plugin.xml maven-core/lifecycle-executor.**txt maven-core/plugin-manager.txt maven-core/project-builder.txt maven-core/src/main/resources/**org/apache/maven/messages/** build.properties maven-core/src/site/apt/**artifact-handlers.apt maven-core/src/site/apt/**configuration-management.apt maven-core/src/site/apt/**default-bindings.apt.vm maven-core/src/site/apt/**getting-to-container-**configured-mojos.apt maven-core/src/site/apt/index.**apt maven-core/src/site/apt/**inheritance.apt maven-core/src/site/apt/**lifecycles.apt.vm maven-core/src/site/apt/**offline-mode.apt maven-core/src/site/apt/**plugin-execution-isolation.apt maven-core/src/site/apt/**scripting-support/marmalade-**support.apt maven-core/src/site/resources/**design/2.1-lifecycle-refactor.**graffle maven-embedder/src/examples/**simple-project/src/main/java/** org/apache/maven/embedder/App.**java maven-embedder/src/examples/**simple-project/src/test/java/** org/apache/maven/embedder/**AppTest.java maven-embedder/src/main/**resources/META-INF/MANIFEST.MF maven-embedder/src/main/**resources/META-INF/maven/** slf4j-configuration.properties maven-embedder/src/site/apt/**cli.apt.vm maven-embedder/src/site/apt/**index.apt.vm
Re: [VOTE] Apache 3.1.0-alpha-1
I will cancel the vote and respin it. No one has looked that hard: there's a snapshot repository in the top-level POM. I haven't made any noise as Hervé is trying to release all the prerequisites so that some of the standard plugins don't fail. On May 2, 2013, at 5:16 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: Currently it's +1 (binding): Hervé me Some other +1's and -1's I'd expect the release manager for ths release to have made some noise by now (as any release manager should) On Thursday, 2 May 2013, Stephen Connolly wrote: I think we are just waiting for one more binding vote from a PMC member... But somebody should double check the count On Thursday, 2 May 2013, ceki wrote: Hello all, Out of curiosity, are there any other non-resolved issues holding up this release? Best regards, On 23.04.2013 12:24, Stephen Connolly wrote: +1 (binding) for 3.1.0-alpha-1 The following issue needs to be resolved before I will vote +1 on a non-alpha release: http://jira.codehaus.org/**browse/MNG-5470http://jira.codehaus.org/browse/MNG-5470 RAT is reporting the 391 files are either missing license headers or have not been flagged as files that cannot support a license header. Most of these are test data files and I would be happy to argue that the test may require a specific exact content for reproducibility, but the following I do not feel I can make a case for. I will require these 39 files to be addressed in some way before the final 3.1.0 release or I cannot provide a binding vote for the release. (the MANIFEST.MF may be one where a header does not make sense, but it is a non-generated file) I cannot speak for the rest of the PMC, but my understanding is that as a PMC member it is one of our duties to ensure that the source (which is what the vote is on) has met with the ASF requirements for license headers. * Unapproved licenses: apache-maven/src/bin/m2.conf apache-maven/src/conf/logging/**simplelogger.properties maven-aether-provider/src/**main/java/org/apache/maven/** repository/internal/package.**html maven-aether-provider/src/**site/apt/index.apt maven-artifact/src/site/apt/**index.apt maven-compat/compatibility.cfl maven-compat/src/main/**resources/META-INF/maven/**plugin.xml maven-core/lifecycle-executor.**txt maven-core/plugin-manager.txt maven-core/project-builder.txt maven-core/src/main/resources/**org/apache/maven/messages/** build.properties maven-core/src/site/apt/**artifact-handlers.apt maven-core/src/site/apt/**configuration-management.apt maven-core/src/site/apt/**default-bindings.apt.vm maven-core/src/site/apt/**getting-to-container-**configured-mojos.apt maven-core/src/site/apt/index.**apt maven-core/src/site/apt/**inheritance.apt maven-core/src/site/apt/**lifecycles.apt.vm maven-core/src/site/apt/**offline-mode.apt maven-core/src/site/apt/**plugin-execution-isolation.apt maven-core/src/site/apt/**scripting-support/marmalade-**support.apt maven-core/src/site/resources/**design/2.1-lifecycle-refactor.**graffle maven-embedder/src/examples/**simple-project/src/main/java/** org/apache/maven/embedder/App.**java maven-embedder/src/examples/**simple-project/src/test/java/** org/apache/maven/embedder/**AppTest.java maven-embedder/src/main/**resources/META-INF/MANIFEST.MF maven-embedder/src/main/**resources/META-INF/maven/** slf4j-configuration.properties maven-embedder/src/site/apt/**cli.apt.vm maven-embedder/src/site/apt/**index.apt.vm maven-embedder/src/site/apt/**logging.apt maven-model/src/main/java/org/**apache/maven/model/io/xpp3/** package.html maven-model/src/main/java/org/**apache/maven/model/merge/**package.html maven-model/src/main/java/org/**apache/maven/model/package.**html maven-model/src/site/apt/**index.apt maven-model-builder/src/site/**apt/index.apt maven-model-builder/src/site/**apt/super-pom.apt.vm maven-plugin-api/src/site/apt/**index.apt maven-plugin-api/src/test/**resources/plugin.xml maven-repository-metadata/src/**site/apt/index.apt maven-settings/src/site/apt/**index.apt Attached is the full report (if it makes it through the mailing list filters) -Stephen On 1 April 2013 13:12, Jason van Zyl ja...@tesla.io mailto:ja...@tesla.io wrote: Here are the release bits for 3.1.0-alpha-1: Release notes: https://jira.codehaus.org/**secure/ReleaseNote.jspa?** projectId=10500version=18967https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=18967 S -- Sent from my phone -- Sent from my phone Thanks, Jason -- Jason van Zyl Founder CTO, Sonatype Founder, Apache Maven http://twitter.com/jvanzyl - Script timed out
Re: [VOTE] Apache 3.1.0-alpha-1
uh, I didn't see this one :( if the check can be automated through an enforcer rule, this would be a Good Thing (TM) I finally found my way with maven-dependency-tree (vote in progress) + dependency:tree (re-added verbose mode, which was a big users expectation). And since I have some time this week (holidays), I should be able to release everything during these holidays. It would be nice to update default plugins in Maven core before the next release candidate. Regards, Hervé Le samedi 4 mai 2013 10:12:25 Jason van Zyl a écrit : I will cancel the vote and respin it. No one has looked that hard: there's a snapshot repository in the top-level POM. I haven't made any noise as Hervé is trying to release all the prerequisites so that some of the standard plugins don't fail. On May 2, 2013, at 5:16 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: Currently it's +1 (binding): Hervé me Some other +1's and -1's I'd expect the release manager for ths release to have made some noise by now (as any release manager should) On Thursday, 2 May 2013, Stephen Connolly wrote: I think we are just waiting for one more binding vote from a PMC member... But somebody should double check the count On Thursday, 2 May 2013, ceki wrote: Hello all, Out of curiosity, are there any other non-resolved issues holding up this release? Best regards, On 23.04.2013 12:24, Stephen Connolly wrote: +1 (binding) for 3.1.0-alpha-1 The following issue needs to be resolved before I will vote +1 on a non-alpha release: http://jira.codehaus.org/**browse/MNG-5470http://jira.codehaus.org/brows e/MNG-5470 RAT is reporting the 391 files are either missing license headers or have not been flagged as files that cannot support a license header. Most of these are test data files and I would be happy to argue that the test may require a specific exact content for reproducibility, but the following I do not feel I can make a case for. I will require these 39 files to be addressed in some way before the final 3.1.0 release or I cannot provide a binding vote for the release. (the MANIFEST.MF may be one where a header does not make sense, but it is a non-generated file) I cannot speak for the rest of the PMC, but my understanding is that as a PMC member it is one of our duties to ensure that the source (which is what the vote is on) has met with the ASF requirements for license headers. * Unapproved licenses: apache-maven/src/bin/m2.conf apache-maven/src/conf/logging/**simplelogger.properties maven-aether-provider/src/**main/java/org/apache/maven/** repository/internal/package.**html maven-aether-provider/src/**site/apt/index.apt maven-artifact/src/site/apt/**index.apt maven-compat/compatibility.cfl maven-compat/src/main/**resources/META-INF/maven/**plugin.xml maven-core/lifecycle-executor.**txt maven-core/plugin-manager.txt maven-core/project-builder.txt maven-core/src/main/resources/**org/apache/maven/messages/** build.properties maven-core/src/site/apt/**artifact-handlers.apt maven-core/src/site/apt/**configuration-management.apt maven-core/src/site/apt/**default-bindings.apt.vm maven-core/src/site/apt/**getting-to-container-**configured-mojos.apt maven-core/src/site/apt/index.**apt maven-core/src/site/apt/**inheritance.apt maven-core/src/site/apt/**lifecycles.apt.vm maven-core/src/site/apt/**offline-mode.apt maven-core/src/site/apt/**plugin-execution-isolation.apt maven-core/src/site/apt/**scripting-support/marmalade-**support.apt maven-core/src/site/resources/**design/2.1-lifecycle-refactor.**graffle maven-embedder/src/examples/**simple-project/src/main/java/** org/apache/maven/embedder/App.**java maven-embedder/src/examples/**simple-project/src/test/java/** org/apache/maven/embedder/**AppTest.java maven-embedder/src/main/**resources/META-INF/MANIFEST.MF maven-embedder/src/main/**resources/META-INF/maven/** slf4j-configuration.properties maven-embedder/src/site/apt/**cli.apt.vm maven-embedder/src/site/apt/**index.apt.vm maven-embedder/src/site/apt/**logging.apt maven-model/src/main/java/org/**apache/maven/model/io/xpp3/** package.html maven-model/src/main/java/org/**apache/maven/model/merge/**package.html maven-model/src/main/java/org/**apache/maven/model/package.**html maven-model/src/site/apt/**index.apt maven-model-builder/src/site/**apt/index.apt maven-model-builder/src/site/**apt/super-pom.apt.vm maven-plugin-api/src/site/apt/**index.apt maven-plugin-api/src/test/**resources/plugin.xml maven-repository-metadata/src/**site/apt/index.apt maven-settings/src/site/apt/**index.apt Attached is the full report (if it makes it through the mailing list filters) -Stephen On
Re: [VOTE] Apache 3.1.0-alpha-1
Sure, update all the plugins. We might as well do all that maintenance work now before the next release. I can look at making an enforcer rule. It's been something I've been meaning at looking at is breaking out all the checks in the release plugin to enforcer rules so they can be used anywhere. Inside and outside the release plugin. On May 4, 2013, at 11:26 AM, Hervé BOUTEMY herve.bout...@free.fr wrote: uh, I didn't see this one :( if the check can be automated through an enforcer rule, this would be a Good Thing (TM) I finally found my way with maven-dependency-tree (vote in progress) + dependency:tree (re-added verbose mode, which was a big users expectation). And since I have some time this week (holidays), I should be able to release everything during these holidays. It would be nice to update default plugins in Maven core before the next release candidate. Regards, Hervé Le samedi 4 mai 2013 10:12:25 Jason van Zyl a écrit : I will cancel the vote and respin it. No one has looked that hard: there's a snapshot repository in the top-level POM. I haven't made any noise as Hervé is trying to release all the prerequisites so that some of the standard plugins don't fail. On May 2, 2013, at 5:16 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: Currently it's +1 (binding): Hervé me Some other +1's and -1's I'd expect the release manager for ths release to have made some noise by now (as any release manager should) On Thursday, 2 May 2013, Stephen Connolly wrote: I think we are just waiting for one more binding vote from a PMC member... But somebody should double check the count On Thursday, 2 May 2013, ceki wrote: Hello all, Out of curiosity, are there any other non-resolved issues holding up this release? Best regards, On 23.04.2013 12:24, Stephen Connolly wrote: +1 (binding) for 3.1.0-alpha-1 The following issue needs to be resolved before I will vote +1 on a non-alpha release: http://jira.codehaus.org/**browse/MNG-5470http://jira.codehaus.org/brows e/MNG-5470 RAT is reporting the 391 files are either missing license headers or have not been flagged as files that cannot support a license header. Most of these are test data files and I would be happy to argue that the test may require a specific exact content for reproducibility, but the following I do not feel I can make a case for. I will require these 39 files to be addressed in some way before the final 3.1.0 release or I cannot provide a binding vote for the release. (the MANIFEST.MF may be one where a header does not make sense, but it is a non-generated file) I cannot speak for the rest of the PMC, but my understanding is that as a PMC member it is one of our duties to ensure that the source (which is what the vote is on) has met with the ASF requirements for license headers. * Unapproved licenses: apache-maven/src/bin/m2.conf apache-maven/src/conf/logging/**simplelogger.properties maven-aether-provider/src/**main/java/org/apache/maven/** repository/internal/package.**html maven-aether-provider/src/**site/apt/index.apt maven-artifact/src/site/apt/**index.apt maven-compat/compatibility.cfl maven-compat/src/main/**resources/META-INF/maven/**plugin.xml maven-core/lifecycle-executor.**txt maven-core/plugin-manager.txt maven-core/project-builder.txt maven-core/src/main/resources/**org/apache/maven/messages/** build.properties maven-core/src/site/apt/**artifact-handlers.apt maven-core/src/site/apt/**configuration-management.apt maven-core/src/site/apt/**default-bindings.apt.vm maven-core/src/site/apt/**getting-to-container-**configured-mojos.apt maven-core/src/site/apt/index.**apt maven-core/src/site/apt/**inheritance.apt maven-core/src/site/apt/**lifecycles.apt.vm maven-core/src/site/apt/**offline-mode.apt maven-core/src/site/apt/**plugin-execution-isolation.apt maven-core/src/site/apt/**scripting-support/marmalade-**support.apt maven-core/src/site/resources/**design/2.1-lifecycle-refactor.**graffle maven-embedder/src/examples/**simple-project/src/main/java/** org/apache/maven/embedder/App.**java maven-embedder/src/examples/**simple-project/src/test/java/** org/apache/maven/embedder/**AppTest.java maven-embedder/src/main/**resources/META-INF/MANIFEST.MF maven-embedder/src/main/**resources/META-INF/maven/** slf4j-configuration.properties maven-embedder/src/site/apt/**cli.apt.vm maven-embedder/src/site/apt/**index.apt.vm maven-embedder/src/site/apt/**logging.apt maven-model/src/main/java/org/**apache/maven/model/io/xpp3/** package.html maven-model/src/main/java/org/**apache/maven/model/merge/**package.html maven-model/src/main/java/org/**apache/maven/model/package.**html maven-model/src/site/apt/**index.apt maven-model-builder/src/site/**apt/index.apt maven-model-builder/src/site/**apt/super-pom.apt.vm
Re: [VOTE] Apache 3.1.0-alpha-1
Hello all, Out of curiosity, are there any other non-resolved issues holding up this release? Best regards, On 23.04.2013 12:24, Stephen Connolly wrote: +1 (binding) for 3.1.0-alpha-1 The following issue needs to be resolved before I will vote +1 on a non-alpha release: http://jira.codehaus.org/browse/MNG-5470 RAT is reporting the 391 files are either missing license headers or have not been flagged as files that cannot support a license header. Most of these are test data files and I would be happy to argue that the test may require a specific exact content for reproducibility, but the following I do not feel I can make a case for. I will require these 39 files to be addressed in some way before the final 3.1.0 release or I cannot provide a binding vote for the release. (the MANIFEST.MF may be one where a header does not make sense, but it is a non-generated file) I cannot speak for the rest of the PMC, but my understanding is that as a PMC member it is one of our duties to ensure that the source (which is what the vote is on) has met with the ASF requirements for license headers. *** Unapproved licenses: apache-maven/src/bin/m2.conf apache-maven/src/conf/logging/simplelogger.properties maven-aether-provider/src/main/java/org/apache/maven/repository/internal/package.html maven-aether-provider/src/site/apt/index.apt maven-artifact/src/site/apt/index.apt maven-compat/compatibility.cfl maven-compat/src/main/resources/META-INF/maven/plugin.xml maven-core/lifecycle-executor.txt maven-core/plugin-manager.txt maven-core/project-builder.txt maven-core/src/main/resources/org/apache/maven/messages/build.properties maven-core/src/site/apt/artifact-handlers.apt maven-core/src/site/apt/configuration-management.apt maven-core/src/site/apt/default-bindings.apt.vm maven-core/src/site/apt/getting-to-container-configured-mojos.apt maven-core/src/site/apt/index.apt maven-core/src/site/apt/inheritance.apt maven-core/src/site/apt/lifecycles.apt.vm maven-core/src/site/apt/offline-mode.apt maven-core/src/site/apt/plugin-execution-isolation.apt maven-core/src/site/apt/scripting-support/marmalade-support.apt maven-core/src/site/resources/design/2.1-lifecycle-refactor.graffle maven-embedder/src/examples/simple-project/src/main/java/org/apache/maven/embedder/App.java maven-embedder/src/examples/simple-project/src/test/java/org/apache/maven/embedder/AppTest.java maven-embedder/src/main/resources/META-INF/MANIFEST.MF maven-embedder/src/main/resources/META-INF/maven/slf4j-configuration.properties maven-embedder/src/site/apt/cli.apt.vm maven-embedder/src/site/apt/index.apt.vm maven-embedder/src/site/apt/logging.apt maven-model/src/main/java/org/apache/maven/model/io/xpp3/package.html maven-model/src/main/java/org/apache/maven/model/merge/package.html maven-model/src/main/java/org/apache/maven/model/package.html maven-model/src/site/apt/index.apt maven-model-builder/src/site/apt/index.apt maven-model-builder/src/site/apt/super-pom.apt.vm maven-plugin-api/src/site/apt/index.apt maven-plugin-api/src/test/resources/plugin.xml maven-repository-metadata/src/site/apt/index.apt maven-settings/src/site/apt/index.apt Attached is the full report (if it makes it through the mailing list filters) -Stephen On 1 April 2013 13:12, Jason van Zyl ja...@tesla.io mailto:ja...@tesla.io wrote: Here are the release bits for 3.1.0-alpha-1: Release notes: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=18967 Staging repository: https://repository.apache.org/content/repositories/maven-042/ Staged distribution: https://repository.apache.org/content/repositories/maven-042/org/apache/maven/apache-maven/3.1.0-alpha-1/ Anyone trying this in advance should know that the Site, Dependency, and Shade plugin are not going to work. We are aware of this and those responsible for those plugins are looking into it. Thanks, Jason -- Jason van Zyl Founder CTO, Sonatype Founder, Apache Maven http://twitter.com/jvanzyl - We know what we are, but know not what we may be. -- Shakespeare -- Ceki 65% of statistics are made up on the spot - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Apache 3.1.0-alpha-1
I think we are just waiting for one more binding vote from a PMC member... But somebody should double check the count On Thursday, 2 May 2013, ceki wrote: Hello all, Out of curiosity, are there any other non-resolved issues holding up this release? Best regards, On 23.04.2013 12:24, Stephen Connolly wrote: +1 (binding) for 3.1.0-alpha-1 The following issue needs to be resolved before I will vote +1 on a non-alpha release: http://jira.codehaus.org/**browse/MNG-5470http://jira.codehaus.org/browse/MNG-5470 RAT is reporting the 391 files are either missing license headers or have not been flagged as files that cannot support a license header. Most of these are test data files and I would be happy to argue that the test may require a specific exact content for reproducibility, but the following I do not feel I can make a case for. I will require these 39 files to be addressed in some way before the final 3.1.0 release or I cannot provide a binding vote for the release. (the MANIFEST.MF may be one where a header does not make sense, but it is a non-generated file) I cannot speak for the rest of the PMC, but my understanding is that as a PMC member it is one of our duties to ensure that the source (which is what the vote is on) has met with the ASF requirements for license headers. * Unapproved licenses: apache-maven/src/bin/m2.conf apache-maven/src/conf/logging/**simplelogger.properties maven-aether-provider/src/**main/java/org/apache/maven/** repository/internal/package.**html maven-aether-provider/src/**site/apt/index.apt maven-artifact/src/site/apt/**index.apt maven-compat/compatibility.cfl maven-compat/src/main/**resources/META-INF/maven/**plugin.xml maven-core/lifecycle-executor.**txt maven-core/plugin-manager.txt maven-core/project-builder.txt maven-core/src/main/resources/**org/apache/maven/messages/** build.properties maven-core/src/site/apt/**artifact-handlers.apt maven-core/src/site/apt/**configuration-management.apt maven-core/src/site/apt/**default-bindings.apt.vm maven-core/src/site/apt/**getting-to-container-**configured-mojos.apt maven-core/src/site/apt/index.**apt maven-core/src/site/apt/**inheritance.apt maven-core/src/site/apt/**lifecycles.apt.vm maven-core/src/site/apt/**offline-mode.apt maven-core/src/site/apt/**plugin-execution-isolation.apt maven-core/src/site/apt/**scripting-support/marmalade-**support.apt maven-core/src/site/resources/**design/2.1-lifecycle-refactor.** graffle maven-embedder/src/examples/**simple-project/src/main/java/** org/apache/maven/embedder/App.**java maven-embedder/src/examples/**simple-project/src/test/java/** org/apache/maven/embedder/**AppTest.java maven-embedder/src/main/**resources/META-INF/MANIFEST.MF maven-embedder/src/main/**resources/META-INF/maven/** slf4j-configuration.properties maven-embedder/src/site/apt/**cli.apt.vm maven-embedder/src/site/apt/**index.apt.vm maven-embedder/src/site/apt/**logging.apt maven-model/src/main/java/org/**apache/maven/model/io/xpp3/** package.html maven-model/src/main/java/org/**apache/maven/model/merge/** package.html maven-model/src/main/java/org/**apache/maven/model/package.**html maven-model/src/site/apt/**index.apt maven-model-builder/src/site/**apt/index.apt maven-model-builder/src/site/**apt/super-pom.apt.vm maven-plugin-api/src/site/apt/**index.apt maven-plugin-api/src/test/**resources/plugin.xml maven-repository-metadata/src/**site/apt/index.apt maven-settings/src/site/apt/**index.apt Attached is the full report (if it makes it through the mailing list filters) -Stephen On 1 April 2013 13:12, Jason van Zyl ja...@tesla.io mailto:ja...@tesla.io wrote: Here are the release bits for 3.1.0-alpha-1: Release notes: https://jira.codehaus.org/**secure/ReleaseNote.jspa?** projectId=10500version=18967https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=18967 Staging repository: https://repository.apache.org/**content/repositories/maven-**042/https://repository.apache.org/content/repositories/maven-042/ Staged distribution: https://repository.apache.org/**content/repositories/maven-** 042/org/apache/maven/apache-**maven/3.1.0-alpha-1/https://repository.apache.org/content/repositories/maven-042/org/apache/maven/apache-maven/3.1.0-alpha-1/ Anyone trying this in advance should know that the Site, Dependency, and Shade plugin are not going to work. We are aware of this and those responsible for those plugins are looking into it. Thanks, Jason --** Jason van Zyl Founder CTO, Sonatype Founder, Apache Maven http://twitter.com/jvanzyl --**--- We know what we are, but
Re: [VOTE] Apache 3.1.0-alpha-1
Currently it's +1 (binding): Hervé me Some other +1's and -1's I'd expect the release manager for ths release to have made some noise by now (as any release manager should) On Thursday, 2 May 2013, Stephen Connolly wrote: I think we are just waiting for one more binding vote from a PMC member... But somebody should double check the count On Thursday, 2 May 2013, ceki wrote: Hello all, Out of curiosity, are there any other non-resolved issues holding up this release? Best regards, On 23.04.2013 12:24, Stephen Connolly wrote: +1 (binding) for 3.1.0-alpha-1 The following issue needs to be resolved before I will vote +1 on a non-alpha release: http://jira.codehaus.org/**browse/MNG-5470http://jira.codehaus.org/browse/MNG-5470 RAT is reporting the 391 files are either missing license headers or have not been flagged as files that cannot support a license header. Most of these are test data files and I would be happy to argue that the test may require a specific exact content for reproducibility, but the following I do not feel I can make a case for. I will require these 39 files to be addressed in some way before the final 3.1.0 release or I cannot provide a binding vote for the release. (the MANIFEST.MF may be one where a header does not make sense, but it is a non-generated file) I cannot speak for the rest of the PMC, but my understanding is that as a PMC member it is one of our duties to ensure that the source (which is what the vote is on) has met with the ASF requirements for license headers. * Unapproved licenses: apache-maven/src/bin/m2.conf apache-maven/src/conf/logging/**simplelogger.properties maven-aether-provider/src/**main/java/org/apache/maven/** repository/internal/package.**html maven-aether-provider/src/**site/apt/index.apt maven-artifact/src/site/apt/**index.apt maven-compat/compatibility.cfl maven-compat/src/main/**resources/META-INF/maven/**plugin.xml maven-core/lifecycle-executor.**txt maven-core/plugin-manager.txt maven-core/project-builder.txt maven-core/src/main/resources/**org/apache/maven/messages/** build.properties maven-core/src/site/apt/**artifact-handlers.apt maven-core/src/site/apt/**configuration-management.apt maven-core/src/site/apt/**default-bindings.apt.vm maven-core/src/site/apt/**getting-to-container-**configured-mojos.apt maven-core/src/site/apt/index.**apt maven-core/src/site/apt/**inheritance.apt maven-core/src/site/apt/**lifecycles.apt.vm maven-core/src/site/apt/**offline-mode.apt maven-core/src/site/apt/**plugin-execution-isolation.apt maven-core/src/site/apt/**scripting-support/marmalade-**support.apt maven-core/src/site/resources/**design/2.1-lifecycle-refactor.**graffle maven-embedder/src/examples/**simple-project/src/main/java/** org/apache/maven/embedder/App.**java maven-embedder/src/examples/**simple-project/src/test/java/** org/apache/maven/embedder/**AppTest.java maven-embedder/src/main/**resources/META-INF/MANIFEST.MF maven-embedder/src/main/**resources/META-INF/maven/** slf4j-configuration.properties maven-embedder/src/site/apt/**cli.apt.vm maven-embedder/src/site/apt/**index.apt.vm maven-embedder/src/site/apt/**logging.apt maven-model/src/main/java/org/**apache/maven/model/io/xpp3/** package.html maven-model/src/main/java/org/**apache/maven/model/merge/**package.html maven-model/src/main/java/org/**apache/maven/model/package.**html maven-model/src/site/apt/**index.apt maven-model-builder/src/site/**apt/index.apt maven-model-builder/src/site/**apt/super-pom.apt.vm maven-plugin-api/src/site/apt/**index.apt maven-plugin-api/src/test/**resources/plugin.xml maven-repository-metadata/src/**site/apt/index.apt maven-settings/src/site/apt/**index.apt Attached is the full report (if it makes it through the mailing list filters) -Stephen On 1 April 2013 13:12, Jason van Zyl ja...@tesla.io mailto:ja...@tesla.io wrote: Here are the release bits for 3.1.0-alpha-1: Release notes: https://jira.codehaus.org/**secure/ReleaseNote.jspa?** projectId=10500version=18967https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=18967 S -- Sent from my phone -- Sent from my phone
Re: [VOTE] Apache 3.1.0-alpha-1
-1 (non binding) I've found an issue with an integration of my plugin developments which works with Maven 3.0.X without any problem but with Maven 3.1-alpha-1 it fails. I've created a gist (https://gist.github.com/khmarbaise/5473941) which shows the whole debug output following only an excerpt: [DEBUG] (f) project = MavenProject: org.codehaus.mojo:build-metadata-maven-plugin-report-it:1.0-SNAPSHOT @ /Users/km/ws-git/build-metadata-maven-plugin/target/it/metadatareport/pom.xml [DEBUG] -- end configuration -- [DEBUG] executing Site Mojo [WARNING] Error injecting: org.apache.maven.reporting.exec.DefaultMavenReportExecutor java.lang.NoClassDefFoundError: org/sonatype/aether/graph/DependencyFilter at java.lang.Class.getDeclaredConstructors0(Native Method) at java.lang.Class.privateGetDeclaredConstructors(Class.java:2389) at java.lang.Class.getDeclaredConstructors(Class.java:1836) Is that a known issue ? Kind regards Karl-Heinz Marbaise -- SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893 Dipl.Ing.(FH) Karl-Heinz MarbaiseICQ#: 135949029 Hauptstrasse 177 USt.IdNr: DE191347579 52146 Würselen http://www.soebes.de - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Apache 3.1.0-alpha-1
On 27 Apr 2013, at 18:52, Karl Heinz Marbaise wrote: -1 (non binding) I've found an issue with an integration of my plugin developments which works with Maven 3.0.X without any problem but with Maven 3.1-alpha-1 it fails. I've created a gist (https://gist.github.com/khmarbaise/5473941) which shows the whole debug output following only an excerpt: [DEBUG] (f) project = MavenProject: org.codehaus.mojo:build-metadata-maven-plugin-report-it:1.0-SNAPSHOT @ /Users/km/ws-git/build-metadata-maven-plugin/target/it/metadatareport/pom.xml [DEBUG] -- end configuration -- [DEBUG] executing Site Mojo [WARNING] Error injecting: org.apache.maven.reporting.exec.DefaultMavenReportExecutor java.lang.NoClassDefFoundError: org/sonatype/aether/graph/DependencyFilter at java.lang.Class.getDeclaredConstructors0(Native Method) at java.lang.Class.privateGetDeclaredConstructors(Class.java:2389) at java.lang.Class.getDeclaredConstructors(Class.java:1836) Is that a known issue ? Yes: http://jira.codehaus.org/browse/MSITE-683 and http://www.mail-archive.com/dev@maven.apache.org/msg96501.html See earlier messages in this vote thread for more information about why this happens and what's been done to address it. Kind regards Karl-Heinz Marbaise -- SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893 Dipl.Ing.(FH) Karl-Heinz MarbaiseICQ#: 135949029 Hauptstrasse 177 USt.IdNr: DE191347579 52146 Würselen http://www.soebes.de - 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: [VOTE] Apache 3.1.0-alpha-1
back to the vote +1 - maven-report-exec 1.1 makes m-site-p work with this release: no need to wait for m-site-p 3.3, we can add instructions on how to use p-site-p 3.x + maven- report-exec 1.1 like http://svn.apache.org/r1467751 - maven-dependency-tree 2.1-SNAPSHOT makes dependency:tree, shade and MPIr:dependencies work too, and I don't mind if the compoentn release hasn't been done for the moment, I prefer continue work on it to improve it as much as possible I didn't have time to test the release on much other components, but for the moment, I didn't found any other problem than the previous expected ones I hope experience from others is the same Regards, Hervé Le mardi 2 avril 2013 19:00:36 Hervé BOUTEMY a écrit : Staged documentation: http://maven.apache.org/ref/3.1.0-alpha-1/ Regards, Hervé Le lundi 1 avril 2013 08:12:09 Jason van Zyl a écrit : Here are the release bits for 3.1.0-alpha-1: Release notes: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version= 18 967 Staging repository: https://repository.apache.org/content/repositories/maven-042/ Staged distribution: https://repository.apache.org/content/repositories/maven-042/org/apache/ma ve n/apache-maven/3.1.0-alpha-1/ Anyone trying this in advance should know that the Site, Dependency, and Shade plugin are not going to work. We are aware of this and those responsible for those plugins are looking into it. Thanks, Jason -- Jason van Zyl Founder CTO, Sonatype Founder, Apache Maven http://twitter.com/jvanzyl - We know what we are, but know not what we may be. -- Shakespeare - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Apache 3.1.0-alpha-1
Does anyone (Igor?) know if there is work going on to make Tycho work with this? /Anders On Fri, Apr 19, 2013 at 8:16 AM, Hervé BOUTEMY herve.bout...@free.frwrote: back to the vote +1 - maven-report-exec 1.1 makes m-site-p work with this release: no need to wait for m-site-p 3.3, we can add instructions on how to use p-site-p 3.x + maven- report-exec 1.1 like http://svn.apache.org/r1467751 - maven-dependency-tree 2.1-SNAPSHOT makes dependency:tree, shade and MPIr:dependencies work too, and I don't mind if the compoentn release hasn't been done for the moment, I prefer continue work on it to improve it as much as possible I didn't have time to test the release on much other components, but for the moment, I didn't found any other problem than the previous expected ones I hope experience from others is the same Regards, Hervé Le mardi 2 avril 2013 19:00:36 Hervé BOUTEMY a écrit : Staged documentation: http://maven.apache.org/ref/3.1.0-alpha-1/ Regards, Hervé Le lundi 1 avril 2013 08:12:09 Jason van Zyl a écrit : Here are the release bits for 3.1.0-alpha-1: Release notes: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version= 18 967 Staging repository: https://repository.apache.org/content/repositories/maven-042/ Staged distribution: https://repository.apache.org/content/repositories/maven-042/org/apache/ma ve n/apache-maven/3.1.0-alpha-1/ Anyone trying this in advance should know that the Site, Dependency, and Shade plugin are not going to work. We are aware of this and those responsible for those plugins are looking into it. Thanks, Jason -- Jason van Zyl Founder CTO, Sonatype Founder, Apache Maven http://twitter.com/jvanzyl - We know what we are, but know not what we may be. -- Shakespeare - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Apache 3.1.0-alpha-1
Not sure, but I've just logged https://bugs.eclipse.org/bugs/show_bug.cgi?id=406056 in the Tycho project so it's at least tracked. On 19 Apr 2013, at 07:53, Anders Hammar wrote: Does anyone (Igor?) know if there is work going on to make Tycho work with this? /Anders On Fri, Apr 19, 2013 at 8:16 AM, Hervé BOUTEMY herve.bout...@free.frwrote: back to the vote +1 - maven-report-exec 1.1 makes m-site-p work with this release: no need to wait for m-site-p 3.3, we can add instructions on how to use p-site-p 3.x + maven- report-exec 1.1 like http://svn.apache.org/r1467751 - maven-dependency-tree 2.1-SNAPSHOT makes dependency:tree, shade and MPIr:dependencies work too, and I don't mind if the compoentn release hasn't been done for the moment, I prefer continue work on it to improve it as much as possible I didn't have time to test the release on much other components, but for the moment, I didn't found any other problem than the previous expected ones I hope experience from others is the same Regards, Hervé Le mardi 2 avril 2013 19:00:36 Hervé BOUTEMY a écrit : Staged documentation: http://maven.apache.org/ref/3.1.0-alpha-1/ Regards, Hervé Le lundi 1 avril 2013 08:12:09 Jason van Zyl a écrit : Here are the release bits for 3.1.0-alpha-1: Release notes: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version= 18 967 Staging repository: https://repository.apache.org/content/repositories/maven-042/ Staged distribution: https://repository.apache.org/content/repositories/maven-042/org/apache/ma ve n/apache-maven/3.1.0-alpha-1/ Anyone trying this in advance should know that the Site, Dependency, and Shade plugin are not going to work. We are aware of this and those responsible for those plugins are looking into it. Thanks, Jason -- Jason van Zyl Founder CTO, Sonatype Founder, Apache Maven http://twitter.com/jvanzyl - We know what we are, but know not what we may be. -- Shakespeare - 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: [VOTE] Apache 3.1.0-alpha-1
On 9 Apr 2013, at 03:33, Hervé BOUTEMY wrote:
I just did the reimport and changed API to let the code compile [1]
but I get Guice provisioning exceptions during tests: probably something
stupid in initialization, but I don't know what to do
Can you help me at this step, please?
You need to enable container auto-wiring in the test because Eclipse/Aether
uses this feature, for example:
diff --git
a/maven-aether-provider/src/test/java/org/apache/maven/repository/internal/AbstractRepositoryTestCase.java
b/maven-aether-provider/src/test/java/org/apache/maven/repository/internal/AbstractRepositoryTestCase.java
index f615a5c..eea3830 100644
---
a/maven-aether-provider/src/test/java/org/apache/maven/repository/internal/AbstractRepositoryTestCase.java
+++
b/maven-aether-provider/src/test/java/org/apache/maven/repository/internal/AbstractRepositoryTestCase.java
@@ -23,6 +23,7 @@
import org.apache.maven.repository.internal.util.ConsoleRepositoryListener;
import org.apache.maven.repository.internal.util.ConsoleTransferListener;
+import org.codehaus.plexus.ContainerConfiguration;
import org.codehaus.plexus.PlexusTestCase;
import org.eclipse.aether.DefaultRepositorySystemSession;
import org.eclipse.aether.RepositorySystem;
@@ -38,6 +39,13 @@
protected RepositorySystemSession session;
@Override
+protected void customizeContainerConfiguration( ContainerConfiguration
containerConfiguration )
+{
+super.customizeContainerConfiguration( containerConfiguration );
+containerConfiguration.setAutoWiring( true );
+}
+
+@Override
protected void setUp()
throws Exception
{
MavenCLI turns auto-wiring on, but these unit tests extend PlexusTestCase which
has this off by default (to mimic the original Plexus behaviour).
HTH
Regards,
Hervé
[1] https://github.com/hboutemy/maven
Le mardi 9 avril 2013 03:33:58 Hervé BOUTEMY a écrit :
Le dimanche 7 avril 2013 22:29:29 Jason van Zyl a écrit :
On Apr 7, 2013, at 7:32 PM, Hervé BOUTEMY herve.bout...@free.fr wrote:
while working on site publication, I found that all my work on
maven-aether- provider unit tests had simply been pruned when merging
Aether. I will need to re-do the work, step by step :(
I don't think you need to redo anything. If you can find the commits I can
work them back in. I'd like to figure out how they got pruned.
yes, I know that using a SCM means that I won't completely re-do it from
scratch but dig into history to find relevant commits then re-apply them.
I already had a look, but these are non-trivial merges because it all starts
with MavenRepositorySystemSession (in maven-aether-provider) class being
removed in favor of MavenRepositorySystemUtils in commit
82b345e0094813b34fcac85e64dde2d5e02b4cc9. Since it was the basis for unit
tests started with commit 5f92449d5d628f3c40f8a4082bcedc369e96bd2d, I fully
understand that there is a strong conflict, even if I can't find where my
classes were removed (if file modification is easy to track, file removal
isn't, or I don't know how to do).
I just tried to cherry pick a commit, but it causes too much conflicts: I'll
better manually get the latest state before delete and work on reimport.
Regards,
Hervé
From my perspective, maven-reporting-exec is ready to release: I'll do
it
tomorrow if nobody objects.
I'd like some review on DOXIA-484 before releasing Doxia 1.4
And I still didn't have a look at dependency:tree...
Regards,
Hervé
Le lundi 1 avril 2013 08:12:09 Jason van Zyl a écrit :
Here are the release bits for 3.1.0-alpha-1:
Release notes:
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500versi
on
=18 967
Staging repository:
https://repository.apache.org/content/repositories/maven-042/
Staged distribution:
https://repository.apache.org/content/repositories/maven-042/org/apache
/m
ave n/apache-maven/3.1.0-alpha-1/
Anyone trying this in advance should know that the Site, Dependency,
and
Shade plugin are not going to work. We are aware of this and those
responsible for those plugins are looking into it.
Thanks,
Jason
--
Jason van Zyl
Founder CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
-
We know what we are, but know not what we may be.
-- Shakespeare
-
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
-
A party which is not afraid of letting culture,
business, and welfare go to ruin completely can
be omnipotent for a
Re: [VOTE] Apache 3.1.0-alpha-1
that's it, it works
thank you Stuart: I knew I was missing something like this = few code but
major structure :)
Regards,
Hervé
Le mardi 9 avril 2013 12:30:31 Stuart McCulloch a écrit :
On 9 Apr 2013, at 03:33, Hervé BOUTEMY wrote:
I just did the reimport and changed API to let the code compile [1]
but I get Guice provisioning exceptions during tests: probably something
stupid in initialization, but I don't know what to do
Can you help me at this step, please?
You need to enable container auto-wiring in the test because Eclipse/Aether
uses this feature, for example:
diff --git
a/maven-aether-provider/src/test/java/org/apache/maven/repository/internal/
AbstractRepositoryTestCase.java
b/maven-aether-provider/src/test/java/org/apache/maven/repository/internal/
AbstractRepositoryTestCase.java index f615a5c..eea3830 100644
---
a/maven-aether-provider/src/test/java/org/apache/maven/repository/internal/
AbstractRepositoryTestCase.java +++
b/maven-aether-provider/src/test/java/org/apache/maven/repository/internal/
AbstractRepositoryTestCase.java @@ -23,6 +23,7 @@
import org.apache.maven.repository.internal.util.ConsoleRepositoryListener;
import org.apache.maven.repository.internal.util.ConsoleTransferListener;
+import org.codehaus.plexus.ContainerConfiguration;
import org.codehaus.plexus.PlexusTestCase;
import org.eclipse.aether.DefaultRepositorySystemSession;
import org.eclipse.aether.RepositorySystem;
@@ -38,6 +39,13 @@
protected RepositorySystemSession session;
@Override
+protected void customizeContainerConfiguration( ContainerConfiguration
containerConfiguration ) +{
+super.customizeContainerConfiguration( containerConfiguration );
+containerConfiguration.setAutoWiring( true );
+}
+
+@Override
protected void setUp()
throws Exception
{
MavenCLI turns auto-wiring on, but these unit tests extend PlexusTestCase
which has this off by default (to mimic the original Plexus behaviour).
HTH
Regards,
Hervé
[1] https://github.com/hboutemy/maven
Le mardi 9 avril 2013 03:33:58 Hervé BOUTEMY a écrit :
Le dimanche 7 avril 2013 22:29:29 Jason van Zyl a écrit :
On Apr 7, 2013, at 7:32 PM, Hervé BOUTEMY herve.bout...@free.fr wrote:
while working on site publication, I found that all my work on
maven-aether- provider unit tests had simply been pruned when merging
Aether. I will need to re-do the work, step by step :(
I don't think you need to redo anything. If you can find the commits I
can
work them back in. I'd like to figure out how they got pruned.
yes, I know that using a SCM means that I won't completely re-do it
from
scratch but dig into history to find relevant commits then re-apply them.
I already had a look, but these are non-trivial merges because it all
starts with MavenRepositorySystemSession (in maven-aether-provider)
class being removed in favor of MavenRepositorySystemUtils in commit
82b345e0094813b34fcac85e64dde2d5e02b4cc9. Since it was the basis for unit
tests started with commit 5f92449d5d628f3c40f8a4082bcedc369e96bd2d, I
fully
understand that there is a strong conflict, even if I can't find where my
classes were removed (if file modification is easy to track, file removal
isn't, or I don't know how to do).
I just tried to cherry pick a commit, but it causes too much conflicts:
I'll better manually get the latest state before delete and work on
reimport.
Regards,
Hervé
From my perspective, maven-reporting-exec is ready to release: I'll do
it
tomorrow if nobody objects.
I'd like some review on DOXIA-484 before releasing Doxia 1.4
And I still didn't have a look at dependency:tree...
Regards,
Hervé
Le lundi 1 avril 2013 08:12:09 Jason van Zyl a écrit :
Here are the release bits for 3.1.0-alpha-1:
Release notes:
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500vers
i
on
=18 967
Staging repository:
https://repository.apache.org/content/repositories/maven-042/
Staged distribution:
https://repository.apache.org/content/repositories/maven-042/org/apach
e
/m
ave n/apache-maven/3.1.0-alpha-1/
Anyone trying this in advance should know that the Site, Dependency,
and
Shade plugin are not going to work. We are aware of this and those
responsible for those plugins are looking into it.
Thanks,
Jason
--
Jason van Zyl
Founder CTO, Sonatype
Founder, Apache Maven
http://twitter.com/jvanzyl
-
We know what we are, but know not what we may be.
-- Shakespeare
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Thanks,
Jason
Re: [VOTE] Apache 3.1.0-alpha-1
this will work as well, thank you for the idea. Original Message Subject: Re: [VOTE] Apache 3.1.0-alpha-1 From: Nigel Magnay nigel.mag...@gmail.com To: Maven Developers List dev@maven.apache.org Date: Tue 09 Apr 2013 03:47:21 AM CDT This keeps coming up, over and over and over. e.g: http://maven.40175.n5.nabble.com/Meta-information-about-dependencies-in-a-pom-td4971927.html The maven 'answer' seems to amount to 'hard cheese, you must re-specify each and every one of your dependencies again in your plugin config'. And then pointing to the configuration horror that is the assembly plugin, and completely ignoring the duplication of, like, every single dependency in your use-case. And if your language has scopes other than the burnt-in ones in maven, double-hard cheese with a cherry on top - welcome to screenfuls of warnings and a non-working transitive dependency mechanism. Despite the fact you're already paying the XML tax (so each dependency takes 5 lines in your POM file, compared to single lines in other tools), *and* the fact that XML has a well-defined capability with namespaces to compatibly extend the data (and have those extensions easy to strip out), maven refuses to contemplate this, it seems. How about project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:karaf=maven:plugin:com.apache:karaf xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd; dependency groupIdcom.example/groupId artifactIdbundle/artifactId version1.0.1/version karaf:osgiStartLevel99/karaf:osgiStartLevel karaf:bootInstalltrue/karaf:bootInstall /dependency On Thu, Apr 4, 2013 at 2:57 PM, Andrei Pozolotin andrei.pozolo...@gmail.com wrote: Hervé: thank you for taking the time to respond. issue at hand: karaf http://karaf.apache.org/ has features.xml, which are built from pom.xml http://karaf.apache.org/manual/latest-2.3.x/users-guide/provisioning.html what is missing from maven is the ability to communicate arbitrary custom attributes on per-dependency basis, such as: provide osgiStartLevel value, to specify to osgi runtime bundle start level: dependency groupIdcom.example/groupId artifactIdbundle/artifactId version1.0.1/version osgiStartLevel99/osgiStartLevel /dependency or provide karafBootInstall flag, to specify that karaf runtime should install this dependency at boot-time vs build-time: dependency groupIdcom.example/groupId artifactIdbundle-feature/artifactId version1.0.1/version classifierfeatures/classifier typexml/type karafBootInstalltrue/karafBootInstall /dependency in lieu of these, karaf-maven-plugin is trying to encode this information via scope https://github.com/apache/karaf/blob/trunk/tooling/karaf-maven-plugin/src/main/java/org/apache/karaf/tooling/features/InstallKarsMojo.java#L215 which contradicts the dependency resolution rules and really does not work. hence my request to relax. is there any other ways to address this need? Andrei Original Message Subject: Re: [VOTE] Apache 3.1.0-alpha-1 From: Hervé BOUTEMY herve.bout...@free.fr To: Maven Developers List dev@maven.apache.org Date: Thu 04 Apr 2013 01:21:32 AM CDT AFAIK, there is nothing relaxed from Mven 3.0.x planned But I don't really understand your case (and miss time to investigate in Karaf). Can you give us a pointer to SCM, or paste such a dependency with custom tags? Regards, Hervé Le mercredi 3 avril 2013 08:51:01 Andrei Pozolotin a écrit : I am curious if 3.1.0 will be more relaxed with custom tags inside dependency? Use case: karaf-maven-plugin uses bizarre conventions on how to map from scope into osgi bundle properties (like start level) because there is no way to have a custom tag in dependency and express this requirement. Original Message Subject: Re: [VOTE] Apache 3.1.0-alpha-1 From: Jason van Zyl ja...@tesla.io To: Maven Developers List dev@maven.apache.org Date: Tue 02 Apr 2013 12:04:18 PM CDT Thanks. On Apr 2, 2013, at 1:00 PM, Hervé BOUTEMY herve.bout...@free.fr wrote: Staged documentation: http://maven.apache.org/ref/3.1.0-alpha-1/ Regards, Hervé Le lundi 1 avril 2013 08:12:09 Jason van Zyl a écrit : Here are the release bits for 3.1.0-alpha-1: Release notes: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500versio n=18 967 Staging repository: https://repository.apache.org/content/repositories/maven-042/ Staged distribution: https://repository.apache.org/content/repositories/maven-042/org/apache/ mave n/apache-maven/3.1.0-alpha-1/ Anyone trying this in advance should know that the Site, Dependency, and Shade plugin are not going to work. We are aware of this and those responsible for those plugins are looking into it. Thanks, Jason
Re: [VOTE] Apache 3.1.0-alpha-1
Le dimanche 7 avril 2013 22:29:29 Jason van Zyl a écrit : On Apr 7, 2013, at 7:32 PM, Hervé BOUTEMY herve.bout...@free.fr wrote: while working on site publication, I found that all my work on maven-aether- provider unit tests had simply been pruned when merging Aether. I will need to re-do the work, step by step :( I don't think you need to redo anything. If you can find the commits I can work them back in. I'd like to figure out how they got pruned. yes, I know that using a SCM means that I won't completely re-do it from scratch but dig into history to find relevant commits then re-apply them. I already had a look, but these are non-trivial merges because it all starts with MavenRepositorySystemSession (in maven-aether-provider) class being removed in favor of MavenRepositorySystemUtils in commit 82b345e0094813b34fcac85e64dde2d5e02b4cc9. Since it was the basis for unit tests started with commit 5f92449d5d628f3c40f8a4082bcedc369e96bd2d, I fully understand that there is a strong conflict, even if I can't find where my classes were removed (if file modification is easy to track, file removal isn't, or I don't know how to do). I just tried to cherry pick a commit, but it causes too much conflicts: I'll better manually get the latest state before delete and work on reimport. Regards, Hervé From my perspective, maven-reporting-exec is ready to release: I'll do it tomorrow if nobody objects. I'd like some review on DOXIA-484 before releasing Doxia 1.4 And I still didn't have a look at dependency:tree... Regards, Hervé Le lundi 1 avril 2013 08:12:09 Jason van Zyl a écrit : Here are the release bits for 3.1.0-alpha-1: Release notes: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version =18 967 Staging repository: https://repository.apache.org/content/repositories/maven-042/ Staged distribution: https://repository.apache.org/content/repositories/maven-042/org/apache/m ave n/apache-maven/3.1.0-alpha-1/ Anyone trying this in advance should know that the Site, Dependency, and Shade plugin are not going to work. We are aware of this and those responsible for those plugins are looking into it. Thanks, Jason -- Jason van Zyl Founder CTO, Sonatype Founder, Apache Maven http://twitter.com/jvanzyl - We know what we are, but know not what we may be. -- Shakespeare - 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 - A party which is not afraid of letting culture, business, and welfare go to ruin completely can be omnipotent for a while. -- Jakob Burckhardt - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Apache 3.1.0-alpha-1
while working on site publication, I found that all my work on maven-aether- provider unit tests had simply been pruned when merging Aether. I will need to re-do the work, step by step :( From my perspective, maven-reporting-exec is ready to release: I'll do it tomorrow if nobody objects. I'd like some review on DOXIA-484 before releasing Doxia 1.4 And I still didn't have a look at dependency:tree... Regards, Hervé Le lundi 1 avril 2013 08:12:09 Jason van Zyl a écrit : Here are the release bits for 3.1.0-alpha-1: Release notes: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=18 967 Staging repository: https://repository.apache.org/content/repositories/maven-042/ Staged distribution: https://repository.apache.org/content/repositories/maven-042/org/apache/mave n/apache-maven/3.1.0-alpha-1/ Anyone trying this in advance should know that the Site, Dependency, and Shade plugin are not going to work. We are aware of this and those responsible for those plugins are looking into it. Thanks, Jason -- Jason van Zyl Founder CTO, Sonatype Founder, Apache Maven http://twitter.com/jvanzyl - We know what we are, but know not what we may be. -- Shakespeare - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Apache 3.1.0-alpha-1
Hervé BOUTEMY wrote: while working on site publication, I found that all my work on maven-aether- provider unit tests had simply been pruned when merging Aether. I will need to re-do the work, step by step:( Hervé - if this is all in git, you should be able to still find all your commits via git reflog, if you find them via there, you can checkout the SHA1 of the commit, create a new branch and merge/cherry pick/rebase etc. etc. and hopefully retrace your steps in a much more simpler fashion than starting from scratch. Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Apache 3.1.0-alpha-1
On Apr 7, 2013, at 7:32 PM, Hervé BOUTEMY herve.bout...@free.fr wrote: while working on site publication, I found that all my work on maven-aether- provider unit tests had simply been pruned when merging Aether. I will need to re-do the work, step by step :( I don't think you need to redo anything. If you can find the commits I can work them back in. I'd like to figure out how they got pruned. From my perspective, maven-reporting-exec is ready to release: I'll do it tomorrow if nobody objects. I'd like some review on DOXIA-484 before releasing Doxia 1.4 And I still didn't have a look at dependency:tree... Regards, Hervé Le lundi 1 avril 2013 08:12:09 Jason van Zyl a écrit : Here are the release bits for 3.1.0-alpha-1: Release notes: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=18 967 Staging repository: https://repository.apache.org/content/repositories/maven-042/ Staged distribution: https://repository.apache.org/content/repositories/maven-042/org/apache/mave n/apache-maven/3.1.0-alpha-1/ Anyone trying this in advance should know that the Site, Dependency, and Shade plugin are not going to work. We are aware of this and those responsible for those plugins are looking into it. Thanks, Jason -- Jason van Zyl Founder CTO, Sonatype Founder, Apache Maven http://twitter.com/jvanzyl - We know what we are, but know not what we may be. -- Shakespeare - 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 - A party which is not afraid of letting culture, business, and welfare go to ruin completely can be omnipotent for a while. -- Jakob Burckhardt
Re: [VOTE] Apache 3.1.0-alpha-1
Hi Andrei, Andrei Pozolotin wrote: *Wayne* 1) in this case I choose madness :-) 2) here is my request: please provide an option to modello or whoever is enforcing strict xml model in maven to relax the rules, so people can use maven they way it fits them, while enforcing the rules by default. Then why don't you use custom properties that follow simple naming conventions? Just run in your mojo through the list of (resolved) dependencies and look if an appropriate custom property has been defined: dependencies ... dependency groupIdcom.example/groupId artifactIdbundle/artifactId version1.0.1/version /dependency dependency groupIdcom.example/groupId artifactIdbundle/artifactId version1.0.1/version classifierfeatures/classifier typexml/type /dependency ... /dependencies ... properties ... karaf.com.example.bundle.osgiStartLevel99/karaf.com.example.bundle.osgiStartLevel karaf.com.example.bundle.features.bootInstalltrue/karaf.com.example.bundle.features.bootInstall ... /properties Obvious naming convention: karaf.groupId.artifactId[.classifier].variable - Jörg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Apache 3.1.0-alpha-1
Jörg: you are right. but for me it feels like violation of http://en.wikipedia.org/wiki/Don't_repeat_yourself http://en.wikipedia.org/wiki/Don%27t_repeat_yourself especially if I have half a hundred entries in pom.xml. Andrei Original Message Subject: Re: [VOTE] Apache 3.1.0-alpha-1 From: Jörg Schaible joerg.schai...@scalaris.com To: dev@maven.apache.org Date: Fri 05 Apr 2013 02:35:06 AM CDT Hi Andrei, Andrei Pozolotin wrote: *Wayne* 1) in this case I choose madness :-) 2) here is my request: please provide an option to modello or whoever is enforcing strict xml model in maven to relax the rules, so people can use maven they way it fits them, while enforcing the rules by default. Then why don't you use custom properties that follow simple naming conventions? Just run in your mojo through the list of (resolved) dependencies and look if an appropriate custom property has been defined: dependencies ... dependency groupIdcom.example/groupId artifactIdbundle/artifactId version1.0.1/version /dependency dependency groupIdcom.example/groupId artifactIdbundle/artifactId version1.0.1/version classifierfeatures/classifier typexml/type /dependency ... /dependencies ... properties ... karaf.com.example.bundle.osgiStartLevel99/karaf.com.example.bundle.osgiStartLevel karaf.com.example.bundle.features.bootInstalltrue/karaf.com.example.bundle.features.bootInstall ... /properties Obvious naming convention: karaf.groupId.artifactId[.classifier].variable - Jörg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Apache 3.1.0-alpha-1
AFAIK, there is nothing relaxed from Mven 3.0.x planned But I don't really understand your case (and miss time to investigate in Karaf). Can you give us a pointer to SCM, or paste such a dependency with custom tags? Regards, Hervé Le mercredi 3 avril 2013 08:51:01 Andrei Pozolotin a écrit : I am curious if 3.1.0 will be more relaxed with custom tags inside dependency? Use case: karaf-maven-plugin uses bizarre conventions on how to map from scope into osgi bundle properties (like start level) because there is no way to have a custom tag in dependency and express this requirement. Original Message Subject: Re: [VOTE] Apache 3.1.0-alpha-1 From: Jason van Zyl ja...@tesla.io To: Maven Developers List dev@maven.apache.org Date: Tue 02 Apr 2013 12:04:18 PM CDT Thanks. On Apr 2, 2013, at 1:00 PM, Hervé BOUTEMY herve.bout...@free.fr wrote: Staged documentation: http://maven.apache.org/ref/3.1.0-alpha-1/ Regards, Hervé Le lundi 1 avril 2013 08:12:09 Jason van Zyl a écrit : Here are the release bits for 3.1.0-alpha-1: Release notes: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500versio n=18 967 Staging repository: https://repository.apache.org/content/repositories/maven-042/ Staged distribution: https://repository.apache.org/content/repositories/maven-042/org/apache/ mave n/apache-maven/3.1.0-alpha-1/ Anyone trying this in advance should know that the Site, Dependency, and Shade plugin are not going to work. We are aware of this and those responsible for those plugins are looking into it. Thanks, Jason -- Jason van Zyl Founder CTO, Sonatype Founder, Apache Maven http://twitter.com/jvanzyl - We know what we are, but know not what we may be. -- Shakespeare - 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 - What matters is not ideas, but the people who have them. Good people can fix bad ideas, but good ideas can't save bad people. -- Paul Graham - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Apache 3.1.0-alpha-1
And lastly.. about the site.. I am not sure where this will go in the form it is on the staging site .. what content on the current site would it replace? I don't understand, please explain Regards, Hervé Le mercredi 3 avril 2013 11:58:36 Manfred Moser a écrit : +1 from me (non binding whatsoever but anyway) I tested it with the build for the android maven plugin and ksoap2-android and a few other projects. Apart from the expected problems with shade, site and dependency plugin the android maven plugin also fails with this due to accessing Aether directly (as expected) Anyway... I would really like to move on and get 3.1.0 out, then adapt the android maven plugin to it and make 3.1 required asap. Is there something happening with this vote at all? Is somebody from the PMC at least looking? And lastly.. about the site.. I am not sure where this will go in the form it is on the staging site .. what content on the current site would it replace? Thanks for all the hard work so far. Lets get this out the door! manfred Original Message Subject: Re: [VOTE] Apache 3.1.0-alpha-1 From: Jason van Zyl ja...@tesla.io To: Maven Developers List dev@maven.apache.org Date: Tue 02 Apr 2013 12:04:18 PM CDT Thanks. On Apr 2, 2013, at 1:00 PM, Hervé BOUTEMY herve.bout...@free.fr wrote: Staged documentation: http://maven.apache.org/ref/3.1.0-alpha-1/ Regards, Hervé Le lundi 1 avril 2013 08:12:09 Jason van Zyl a écrit : Here are the release bits for 3.1.0-alpha-1: Release notes: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500versi on=18 967 Staging repository: https://repository.apache.org/content/repositories/maven-042/ Staged distribution: https://repository.apache.org/content/repositories/maven-042/org/apache /mave n/apache-maven/3.1.0-alpha-1/ Anyone trying this in advance should know that the Site, Dependency, and Shade plugin are not going to work. We are aware of this and those responsible for those plugins are looking into it. Thanks, Jason -- Jason van Zyl Founder CTO, Sonatype Founder, Apache Maven http://twitter.com/jvanzyl - We know what we are, but know not what we may be. -- Shakespeare - 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 - What matters is not ideas, but the people who have them. Good people can fix bad ideas, but good ideas can't save bad people. -- Paul Graham - 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
