Re: Apache Maven distribution with fixes
On Aug 16, 2011, at 10:21 AM, Arnaud Héritier wrote: And thus, what's new ??? 3.0.4 is again lost somewhere ... Mark did you have the opportunity to work on the fix you wanted to ? The release is still ready to go. I'm not sure where the vote stands on the EPL licensed 3rd party libraries. I'll let John manage that as the PMC chair. FWIW, the creation reviews for Aether and Sisu start this week and will conclude next Wednesday at which point Sisu and Aether will be official Eclipse projects. Some people voting were positive contingent upon the libraries being at Eclipse proper. This transfer will be complete next week. Arnaud On Fri, Jul 29, 2011 at 8:44 AM, Hervé BOUTEMY herve.bout...@free.frwrote: +1 Regards, Hervé Le jeudi 28 juillet 2011, Brett Porter a écrit : On 28/07/2011, at 10:32 PM, Jason van Zyl wrote: On Jul 28, 2011, at 8:25 AM, Mark Struberg wrote: mom jason. Before we ship 3.0.4 I'd like to fix the SCM URL postfix problem which exists in lots of DSCMs. Will do this in the next week. You probably have 6-7 weeks before an official 3.0.4 release would be made so you have plenty of time. If you are going to wait for Aether and Sisu to be provisioned at Eclipse then the total time for both of those to pass into that state is about 7 weeks. The build I proposed could not be an official release until such a time because there are fixes which rely on Sisu and Aether which are important for users. Would you consider dual licensing them again so we can just keep moving forward as we had been? It makes no changes to your plans and reduces the amount of uncertainty everyone has. It's changed license 3 times in the last year, one more won't hurt. There'd be no hold up if the current release had kept the license that it had when it was incorporated a year ago, and the 3.0.4 release process could start straight away. - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter - 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, Apache Maven http://twitter.com/jvanzyl - the course of true love never did run smooth ... -- Shakespeare
Re: Apache Maven distribution with fixes
Yes, we can go on with releasing 3.0.4. The SCM-Url thingy was decided to be postponed until we have a clear understanding how we cope with pom-4.0.1 (use of xml attributes). LieGrue, strub --- On Tue, 8/16/11, Arnaud Héritier aherit...@gmail.com wrote: From: Arnaud Héritier aherit...@gmail.com Subject: Re: Apache Maven distribution with fixes To: Maven Developers List dev@maven.apache.org Date: Tuesday, August 16, 2011, 2:21 PM And thus, what's new ??? 3.0.4 is again lost somewhere ... Mark did you have the opportunity to work on the fix you wanted to ? Arnaud On Fri, Jul 29, 2011 at 8:44 AM, Hervé BOUTEMY herve.bout...@free.frwrote: +1 Regards, Hervé Le jeudi 28 juillet 2011, Brett Porter a écrit : On 28/07/2011, at 10:32 PM, Jason van Zyl wrote: On Jul 28, 2011, at 8:25 AM, Mark Struberg wrote: mom jason. Before we ship 3.0.4 I'd like to fix the SCM URL postfix problem which exists in lots of DSCMs. Will do this in the next week. You probably have 6-7 weeks before an official 3.0.4 release would be made so you have plenty of time. If you are going to wait for Aether and Sisu to be provisioned at Eclipse then the total time for both of those to pass into that state is about 7 weeks. The build I proposed could not be an official release until such a time because there are fixes which rely on Sisu and Aether which are important for users. Would you consider dual licensing them again so we can just keep moving forward as we had been? It makes no changes to your plans and reduces the amount of uncertainty everyone has. It's changed license 3 times in the last year, one more won't hurt. There'd be no hold up if the current release had kept the license that it had when it was incorporated a year ago, and the 3.0.4 release process could start straight away. - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter - 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: Apache Maven distribution with fixes
ok, thus we loose again some time for nothing. Thus now that Aether and Sisu will be published soon from Eclipse.org with EPL license we need to launch a vote to validate their inclusion ? http://maven.apache.org/developers/dependency-policies.html I will launch the vote. At least we'll be able to see how we'll release 3.0.4 with or without these deps and will be ready to release 3.0.4 at the end of august if we accept them. Arnaud On Wed, Aug 17, 2011 at 3:08 PM, Mark Struberg strub...@yahoo.de wrote: Yes, we can go on with releasing 3.0.4. The SCM-Url thingy was decided to be postponed until we have a clear understanding how we cope with pom-4.0.1 (use of xml attributes). LieGrue, strub --- On Tue, 8/16/11, Arnaud Héritier aherit...@gmail.com wrote: From: Arnaud Héritier aherit...@gmail.com Subject: Re: Apache Maven distribution with fixes To: Maven Developers List dev@maven.apache.org Date: Tuesday, August 16, 2011, 2:21 PM And thus, what's new ??? 3.0.4 is again lost somewhere ... Mark did you have the opportunity to work on the fix you wanted to ? Arnaud On Fri, Jul 29, 2011 at 8:44 AM, Hervé BOUTEMY herve.bout...@free.fr wrote: +1 Regards, Hervé Le jeudi 28 juillet 2011, Brett Porter a écrit : On 28/07/2011, at 10:32 PM, Jason van Zyl wrote: On Jul 28, 2011, at 8:25 AM, Mark Struberg wrote: mom jason. Before we ship 3.0.4 I'd like to fix the SCM URL postfix problem which exists in lots of DSCMs. Will do this in the next week. You probably have 6-7 weeks before an official 3.0.4 release would be made so you have plenty of time. If you are going to wait for Aether and Sisu to be provisioned at Eclipse then the total time for both of those to pass into that state is about 7 weeks. The build I proposed could not be an official release until such a time because there are fixes which rely on Sisu and Aether which are important for users. Would you consider dual licensing them again so we can just keep moving forward as we had been? It makes no changes to your plans and reduces the amount of uncertainty everyone has. It's changed license 3 times in the last year, one more won't hurt. There'd be no hold up if the current release had kept the license that it had when it was incorporated a year ago, and the 3.0.4 release process could start straight away. - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter - 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: Apache Maven distribution with fixes
And thus, what's new ??? 3.0.4 is again lost somewhere ... Mark did you have the opportunity to work on the fix you wanted to ? Arnaud On Fri, Jul 29, 2011 at 8:44 AM, Hervé BOUTEMY herve.bout...@free.frwrote: +1 Regards, Hervé Le jeudi 28 juillet 2011, Brett Porter a écrit : On 28/07/2011, at 10:32 PM, Jason van Zyl wrote: On Jul 28, 2011, at 8:25 AM, Mark Struberg wrote: mom jason. Before we ship 3.0.4 I'd like to fix the SCM URL postfix problem which exists in lots of DSCMs. Will do this in the next week. You probably have 6-7 weeks before an official 3.0.4 release would be made so you have plenty of time. If you are going to wait for Aether and Sisu to be provisioned at Eclipse then the total time for both of those to pass into that state is about 7 weeks. The build I proposed could not be an official release until such a time because there are fixes which rely on Sisu and Aether which are important for users. Would you consider dual licensing them again so we can just keep moving forward as we had been? It makes no changes to your plans and reduces the amount of uncertainty everyone has. It's changed license 3 times in the last year, one more won't hurt. There'd be no hold up if the current release had kept the license that it had when it was incorporated a year ago, and the 3.0.4 release process could start straight away. - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter - 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: Apache Maven distribution with fixes
+1 Regards, Hervé Le jeudi 28 juillet 2011, Brett Porter a écrit : On 28/07/2011, at 10:32 PM, Jason van Zyl wrote: On Jul 28, 2011, at 8:25 AM, Mark Struberg wrote: mom jason. Before we ship 3.0.4 I'd like to fix the SCM URL postfix problem which exists in lots of DSCMs. Will do this in the next week. You probably have 6-7 weeks before an official 3.0.4 release would be made so you have plenty of time. If you are going to wait for Aether and Sisu to be provisioned at Eclipse then the total time for both of those to pass into that state is about 7 weeks. The build I proposed could not be an official release until such a time because there are fixes which rely on Sisu and Aether which are important for users. Would you consider dual licensing them again so we can just keep moving forward as we had been? It makes no changes to your plans and reduces the amount of uncertainty everyone has. It's changed license 3 times in the last year, one more won't hurt. There'd be no hold up if the current release had kept the license that it had when it was incorporated a year ago, and the 3.0.4 release process could start straight away. - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter - 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: Apache Maven distribution with fixes
I'll assume that this is fine and no one objects. I'll announce this on the user list later today. On Jul 27, 2011, at 10:48 AM, Jason van Zyl wrote: Maven PMC, Benjamin and I would like to make a distribution available that addresses several issues with the Apache Maven 3.0.3 release. We have pushed back all bugfixes that do not involve Eclipse Aether[a] and Eclipse Sisu[b] as their incorporation into the mainline and an official release is your decision. We haven't pushed any individual artifacts to Maven Central as part of creating the distribution, we have only created the distribution itself. If there is anything you want changed let us know and we'll change it, but we wanted to make these fixes available in a build for users who are having problems. We're not trying to represent it as anything other then a distribution that incorporates fixes users need. The build is available here: http://people.apache.org/~jvanzyl Summary of the issues Fixes pushed back to the ASF: [MNG-5064][1] mvn -nsu (--no-snapshot-updates) should not download snapshots (and break local builds) [MNG-5131][2] Wrong encoding for encrypted passwords [MNG-5113][3] NullPointerException on javadoc site generation [MNG-5137][4] Reactor resolution does not work for forked multi module builds [MNG-5096][5] exclusion on dependency with typetest-jar/type doesn't work in maven 3 [MNG-5135][6] Regression: in some cases aggregator mojo is unable to resolve dependencies with custom packaging Fixes not pushed back to the ASF as these are dependent on fixes in Eclipse Aether and Eclipse Sisu: [MNG-5042][7] Regression: CloningClassLoader causes StackOverflowError in groovy [MNG-5056][8] Test dependencies get packaged into WAR file. [MNG-5084][9] Resolver for plugins failing [MNG-5087][10] Maven 3 dependency resolution fails until maven-metadata-local.xml files (created by maven-invoker-plugin) are deleted [MNG-5125] [11]Regression: mvn 3.0.3 is extreemly slow with a large number of dependencies [MNG-5138][12] Dependency conflicts are extremely opaque [1]: http://jira.codehaus.org/browse/MNG-5064 [2]: http://jira.codehaus.org/browse/MNG-5131 [3]: http://jira.codehaus.org/browse/MNG-5113 [4]: http://jira.codehaus.org/browse/MNG-5137 [5]: http://jira.codehaus.org/browse/MNG-5096 [6]: http://jira.codehaus.org/browse/MNG-5135 [7]: http://jira.codehaus.org/browse/MNG-5042 [8]: http://jira.codehaus.org/browse/MNG-5056 [9]: http://jira.codehaus.org/browse/MNG-5084 [10]: http://jira.codehaus.org/browse/MNG-5087 [11]: http://jira.codehaus.org/browse/MNG-5125 [12]: http://jira.codehaus.org/browse/MNG-5138 [a]: http://eclipse.org/proposals/technology.aether/ [b]: http://eclipse.org/proposals/technology.sisu/ Thanks, Jason -- Jason van Zyl Eclipse Board Member Founder, Apache Maven http://twitter.com/jvanzyl - If I find ten thousand ways something won't work, I haven't failed. I am not discouraged, because every wrong attempt discarded is just one more step forward. -- Thomas Edison Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl - Our achievements speak for themselves. What we have to keep track of are our failures, discouragements and doubts. We tend to forget the past difficulties, the many false starts, and the painful groping. We see our past achievements as the end result of a clean forward thrust, and our present difficulties as signs of decline and decay. -- Eric Hoffer, Reflections on the Human Condition
Re: Apache Maven distribution with fixes
mom jason. Before we ship 3.0.4 I'd like to fix the SCM URL postfix problem which exists in lots of DSCMs. Will do this in the next week. LieGrue, strub --- On Thu, 7/28/11, Jason van Zyl ja...@sonatype.com wrote: From: Jason van Zyl ja...@sonatype.com Subject: Re: Apache Maven distribution with fixes To: Maven Developers List dev@maven.apache.org Date: Thursday, July 28, 2011, 11:41 AM I'll assume that this is fine and no one objects. I'll announce this on the user list later today. On Jul 27, 2011, at 10:48 AM, Jason van Zyl wrote: Maven PMC, Benjamin and I would like to make a distribution available that addresses several issues with the Apache Maven 3.0.3 release. We have pushed back all bugfixes that do not involve Eclipse Aether[a] and Eclipse Sisu[b] as their incorporation into the mainline and an official release is your decision. We haven't pushed any individual artifacts to Maven Central as part of creating the distribution, we have only created the distribution itself. If there is anything you want changed let us know and we'll change it, but we wanted to make these fixes available in a build for users who are having problems. We're not trying to represent it as anything other then a distribution that incorporates fixes users need. The build is available here: http://people.apache.org/~jvanzyl Summary of the issues Fixes pushed back to the ASF: [MNG-5064][1] mvn -nsu (--no-snapshot-updates) should not download snapshots (and break local builds) [MNG-5131][2] Wrong encoding for encrypted passwords [MNG-5113][3] NullPointerException on javadoc site generation [MNG-5137][4] Reactor resolution does not work for forked multi module builds [MNG-5096][5] exclusion on dependency with typetest-jar/type doesn't work in maven 3 [MNG-5135][6] Regression: in some cases aggregator mojo is unable to resolve dependencies with custom packaging Fixes not pushed back to the ASF as these are dependent on fixes in Eclipse Aether and Eclipse Sisu: [MNG-5042][7] Regression: CloningClassLoader causes StackOverflowError in groovy [MNG-5056][8] Test dependencies get packaged into WAR file. [MNG-5084][9] Resolver for plugins failing [MNG-5087][10] Maven 3 dependency resolution fails until maven-metadata-local.xml files (created by maven-invoker-plugin) are deleted [MNG-5125] [11]Regression: mvn 3.0.3 is extreemly slow with a large number of dependencies [MNG-5138][12] Dependency conflicts are extremely opaque [1]: http://jira.codehaus.org/browse/MNG-5064 [2]: http://jira.codehaus.org/browse/MNG-5131 [3]: http://jira.codehaus.org/browse/MNG-5113 [4]: http://jira.codehaus.org/browse/MNG-5137 [5]: http://jira.codehaus.org/browse/MNG-5096 [6]: http://jira.codehaus.org/browse/MNG-5135 [7]: http://jira.codehaus.org/browse/MNG-5042 [8]: http://jira.codehaus.org/browse/MNG-5056 [9]: http://jira.codehaus.org/browse/MNG-5084 [10]: http://jira.codehaus.org/browse/MNG-5087 [11]: http://jira.codehaus.org/browse/MNG-5125 [12]: http://jira.codehaus.org/browse/MNG-5138 [a]: http://eclipse.org/proposals/technology.aether/ [b]: http://eclipse.org/proposals/technology.sisu/ Thanks, Jason -- Jason van Zyl Eclipse Board Member Founder, Apache Maven http://twitter.com/jvanzyl - If I find ten thousand ways something won't work, I haven't failed. I am not discouraged, because every wrong attempt discarded is just one more step forward. -- Thomas Edison Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl - Our achievements speak for themselves. What we have to keep track of are our failures, discouragements and doubts. We tend to forget the past difficulties, the many false starts, and the painful groping. We see our past achievements as the end result of a clean forward thrust, and our present difficulties as signs of decline and decay. -- Eric Hoffer, Reflections on the Human Condition - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Apache Maven distribution with fixes
On Thu, Jul 28, 2011 at 8:25 AM, Mark Struberg strub...@yahoo.de wrote: mom jason. Before we ship 3.0.4 I'd like to fix the SCM URL postfix problem which exists in lots of DSCMs. Will do this in the next week. Unless there are a lot of pmc members hiding under a rock who aren't voting +1, 3.0.4 can't incorporate the new Aether, and one of the important bug fixes is in there. So we either hold for the Eclipse stand-up of aether, or release without fixing that problem. LieGrue, strub --- On Thu, 7/28/11, Jason van Zyl ja...@sonatype.com wrote: From: Jason van Zyl ja...@sonatype.com Subject: Re: Apache Maven distribution with fixes To: Maven Developers List dev@maven.apache.org Date: Thursday, July 28, 2011, 11:41 AM I'll assume that this is fine and no one objects. I'll announce this on the user list later today. On Jul 27, 2011, at 10:48 AM, Jason van Zyl wrote: Maven PMC, Benjamin and I would like to make a distribution available that addresses several issues with the Apache Maven 3.0.3 release. We have pushed back all bugfixes that do not involve Eclipse Aether[a] and Eclipse Sisu[b] as their incorporation into the mainline and an official release is your decision. We haven't pushed any individual artifacts to Maven Central as part of creating the distribution, we have only created the distribution itself. If there is anything you want changed let us know and we'll change it, but we wanted to make these fixes available in a build for users who are having problems. We're not trying to represent it as anything other then a distribution that incorporates fixes users need. The build is available here: http://people.apache.org/~jvanzyl Summary of the issues Fixes pushed back to the ASF: [MNG-5064][1] mvn -nsu (--no-snapshot-updates) should not download snapshots (and break local builds) [MNG-5131][2] Wrong encoding for encrypted passwords [MNG-5113][3] NullPointerException on javadoc site generation [MNG-5137][4] Reactor resolution does not work for forked multi module builds [MNG-5096][5] exclusion on dependency with typetest-jar/type doesn't work in maven 3 [MNG-5135][6] Regression: in some cases aggregator mojo is unable to resolve dependencies with custom packaging Fixes not pushed back to the ASF as these are dependent on fixes in Eclipse Aether and Eclipse Sisu: [MNG-5042][7] Regression: CloningClassLoader causes StackOverflowError in groovy [MNG-5056][8] Test dependencies get packaged into WAR file. [MNG-5084][9] Resolver for plugins failing [MNG-5087][10] Maven 3 dependency resolution fails until maven-metadata-local.xml files (created by maven-invoker-plugin) are deleted [MNG-5125] [11]Regression: mvn 3.0.3 is extreemly slow with a large number of dependencies [MNG-5138][12] Dependency conflicts are extremely opaque [1]: http://jira.codehaus.org/browse/MNG-5064 [2]: http://jira.codehaus.org/browse/MNG-5131 [3]: http://jira.codehaus.org/browse/MNG-5113 [4]: http://jira.codehaus.org/browse/MNG-5137 [5]: http://jira.codehaus.org/browse/MNG-5096 [6]: http://jira.codehaus.org/browse/MNG-5135 [7]: http://jira.codehaus.org/browse/MNG-5042 [8]: http://jira.codehaus.org/browse/MNG-5056 [9]: http://jira.codehaus.org/browse/MNG-5084 [10]: http://jira.codehaus.org/browse/MNG-5087 [11]: http://jira.codehaus.org/browse/MNG-5125 [12]: http://jira.codehaus.org/browse/MNG-5138 [a]: http://eclipse.org/proposals/technology.aether/ [b]: http://eclipse.org/proposals/technology.sisu/ Thanks, Jason -- Jason van Zyl Eclipse Board Member Founder, Apache Maven http://twitter.com/jvanzyl - If I find ten thousand ways something won't work, I haven't failed. I am not discouraged, because every wrong attempt discarded is just one more step forward. -- Thomas Edison Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl - Our achievements speak for themselves. What we have to keep track of are our failures, discouragements and doubts. We tend to forget the past difficulties, the many false starts, and the painful groping. We see our past achievements as the end result of a clean forward thrust, and our present difficulties as signs of decline and decay. -- Eric Hoffer, Reflections on the Human Condition - 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
Re: Apache Maven distribution with fixes
On 28/07/2011, at 10:32 PM, Jason van Zyl wrote: On Jul 28, 2011, at 8:25 AM, Mark Struberg wrote: mom jason. Before we ship 3.0.4 I'd like to fix the SCM URL postfix problem which exists in lots of DSCMs. Will do this in the next week. You probably have 6-7 weeks before an official 3.0.4 release would be made so you have plenty of time. If you are going to wait for Aether and Sisu to be provisioned at Eclipse then the total time for both of those to pass into that state is about 7 weeks. The build I proposed could not be an official release until such a time because there are fixes which rely on Sisu and Aether which are important for users. Would you consider dual licensing them again so we can just keep moving forward as we had been? It makes no changes to your plans and reduces the amount of uncertainty everyone has. It's changed license 3 times in the last year, one more won't hurt. There'd be no hold up if the current release had kept the license that it had when it was incorporated a year ago, and the 3.0.4 release process could start straight away. - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Apache Maven distribution with fixes
On Thursday, July 28, 2011 7:41:16 AM Jason van Zyl wrote: I'll assume that this is fine and no one objects. I'll announce this on the user list later today. *THAT* I have a problem with.I don't consider these any different than our nightly snapshots or a different commercial build of an Apache project. In both of those cases, announcements about them or promoting them over the official project supplied releases is, IMO, not acceptable on the *users* list. If you want to point a couple of your users at them to help test things or similar, fine as a lead up to 3.0.4. But they cannot be considered general available things similar to releases. Dan On Jul 27, 2011, at 10:48 AM, Jason van Zyl wrote: Maven PMC, Benjamin and I would like to make a distribution available that addresses several issues with the Apache Maven 3.0.3 release. We have pushed back all bugfixes that do not involve Eclipse Aether[a] and Eclipse Sisu[b] as their incorporation into the mainline and an official release is your decision. We haven't pushed any individual artifacts to Maven Central as part of creating the distribution, we have only created the distribution itself. If there is anything you want changed let us know and we'll change it, but we wanted to make these fixes available in a build for users who are having problems. We're not trying to represent it as anything other then a distribution that incorporates fixes users need. The build is available here: http://people.apache.org/~jvanzyl Summary of the issues Fixes pushed back to the ASF: [MNG-5064][1] mvn -nsu (--no-snapshot-updates) should not download snapshots (and break local builds) [MNG-5131][2] Wrong encoding for encrypted passwords [MNG-5113][3] NullPointerException on javadoc site generation [MNG-5137][4] Reactor resolution does not work for forked multi module builds [MNG-5096][5] exclusion on dependency with typetest-jar/type doesn't work in maven 3 [MNG-5135][6] Regression: in some cases aggregator mojo is unable to resolve dependencies with custom packaging Fixes not pushed back to the ASF as these are dependent on fixes in Eclipse Aether and Eclipse Sisu: [MNG-5042][7] Regression: CloningClassLoader causes StackOverflowError in groovy [MNG-5056][8] Test dependencies get packaged into WAR file. [MNG-5084][9] Resolver for plugins failing [MNG-5087][10] Maven 3 dependency resolution fails until maven-metadata-local.xml files (created by maven-invoker-plugin) are deleted [MNG-5125] [11]Regression: mvn 3.0.3 is extreemly slow with a large number of dependencies [MNG-5138][12] Dependency conflicts are extremely opaque [1]: http://jira.codehaus.org/browse/MNG-5064 [2]: http://jira.codehaus.org/browse/MNG-5131 [3]: http://jira.codehaus.org/browse/MNG-5113 [4]: http://jira.codehaus.org/browse/MNG-5137 [5]: http://jira.codehaus.org/browse/MNG-5096 [6]: http://jira.codehaus.org/browse/MNG-5135 [7]: http://jira.codehaus.org/browse/MNG-5042 [8]: http://jira.codehaus.org/browse/MNG-5056 [9]: http://jira.codehaus.org/browse/MNG-5084 [10]: http://jira.codehaus.org/browse/MNG-5087 [11]: http://jira.codehaus.org/browse/MNG-5125 [12]: http://jira.codehaus.org/browse/MNG-5138 [a]: http://eclipse.org/proposals/technology.aether/ [b]: http://eclipse.org/proposals/technology.sisu/ Thanks, Jason -- Jason van Zyl Eclipse Board Member Founder, Apache Maven http://twitter.com/jvanzyl - If I find ten thousand ways something won't work, I haven't failed. I am not discouraged, because every wrong attempt discarded is just one more step forward. -- Thomas Edison Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl - Our achievements speak for themselves. What we have to keep track of are our failures, discouragements and doubts. We tend to forget the past difficulties, the many false starts, and the painful groping. We see our past achievements as the end result of a clean forward thrust, and our present difficulties as signs of decline and decay. -- Eric Hoffer, Reflections on the Human Condition -- Daniel Kulp dk...@apache.org http://dankulp.com/blog Talend - http://www.talend.com - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Apache Maven distribution with fixes
Humm, guess there are only 3 options left in this case 1.) We wait 7 weeks or whatever time it takes (most probably it _will_ take more) 2.) You ship an ALv2 licensed version of Aether and Sisu which we can incorporate into an upcoming maven-3.0.4. 3.) We fork the last ALv2 licensed Aether version back to the Maven project and fix the bugs ourself. LieGrue, strub --- On Thu, 7/28/11, Jason van Zyl ja...@sonatype.com wrote: From: Jason van Zyl ja...@sonatype.com Subject: Re: Apache Maven distribution with fixes To: Maven Developers List dev@maven.apache.org Date: Thursday, July 28, 2011, 12:32 PM On Jul 28, 2011, at 8:25 AM, Mark Struberg wrote: mom jason. Before we ship 3.0.4 I'd like to fix the SCM URL postfix problem which exists in lots of DSCMs. Will do this in the next week. You probably have 6-7 weeks before an official 3.0.4 release would be made so you have plenty of time. If you are going to wait for Aether and Sisu to be provisioned at Eclipse then the total time for both of those to pass into that state is about 7 weeks. The build I proposed could not be an official release until such a time because there are fixes which rely on Sisu and Aether which are important for users. LieGrue, strub --- On Thu, 7/28/11, Jason van Zyl ja...@sonatype.com wrote: From: Jason van Zyl ja...@sonatype.com Subject: Re: Apache Maven distribution with fixes To: Maven Developers List dev@maven.apache.org Date: Thursday, July 28, 2011, 11:41 AM I'll assume that this is fine and no one objects. I'll announce this on the user list later today. On Jul 27, 2011, at 10:48 AM, Jason van Zyl wrote: Maven PMC, Benjamin and I would like to make a distribution available that addresses several issues with the Apache Maven 3.0.3 release. We have pushed back all bugfixes that do not involve Eclipse Aether[a] and Eclipse Sisu[b] as their incorporation into the mainline and an official release is your decision. We haven't pushed any individual artifacts to Maven Central as part of creating the distribution, we have only created the distribution itself. If there is anything you want changed let us know and we'll change it, but we wanted to make these fixes available in a build for users who are having problems. We're not trying to represent it as anything other then a distribution that incorporates fixes users need. The build is available here: http://people.apache.org/~jvanzyl Summary of the issues Fixes pushed back to the ASF: [MNG-5064][1] mvn -nsu (--no-snapshot-updates) should not download snapshots (and break local builds) [MNG-5131][2] Wrong encoding for encrypted passwords [MNG-5113][3] NullPointerException on javadoc site generation [MNG-5137][4] Reactor resolution does not work for forked multi module builds [MNG-5096][5] exclusion on dependency with typetest-jar/type doesn't work in maven 3 [MNG-5135][6] Regression: in some cases aggregator mojo is unable to resolve dependencies with custom packaging Fixes not pushed back to the ASF as these are dependent on fixes in Eclipse Aether and Eclipse Sisu: [MNG-5042][7] Regression: CloningClassLoader causes StackOverflowError in groovy [MNG-5056][8] Test dependencies get packaged into WAR file. [MNG-5084][9] Resolver for plugins failing [MNG-5087][10] Maven 3 dependency resolution fails until maven-metadata-local.xml files (created by maven-invoker-plugin) are deleted [MNG-5125] [11]Regression: mvn 3.0.3 is extreemly slow with a large number of dependencies [MNG-5138][12] Dependency conflicts are extremely opaque [1]: http://jira.codehaus.org/browse/MNG-5064 [2]: http://jira.codehaus.org/browse/MNG-5131 [3]: http://jira.codehaus.org/browse/MNG-5113 [4]: http://jira.codehaus.org/browse/MNG-5137 [5]: http://jira.codehaus.org/browse/MNG-5096 [6]: http://jira.codehaus.org/browse/MNG-5135 [7]: http://jira.codehaus.org/browse/MNG-5042 [8]: http://jira.codehaus.org/browse/MNG-5056 [9]: http://jira.codehaus.org/browse/MNG-5084 [10]: http://jira.codehaus.org/browse/MNG-5087 [11]: http://jira.codehaus.org/browse/MNG-5125 [12]: http://jira.codehaus.org/browse/MNG-5138 [a]: http://eclipse.org/proposals/technology.aether/ [b]: http://eclipse.org/proposals/technology.sisu/ Thanks, Jason -- Jason van Zyl Eclipse Board Member Founder, Apache Maven http://twitter.com/jvanzyl - If I find ten thousand ways something won't work, I haven't failed. I am not discouraged, because every wrong attempt discarded is just one more step forward. -- Thomas Edison Thanks, Jason
Re: Apache Maven distribution with fixes
On Jul 28, 2011, at 8:49 AM, Daniel Kulp wrote: On Thursday, July 28, 2011 7:41:16 AM Jason van Zyl wrote: I'll assume that this is fine and no one objects. I'll announce this on the user list later today. *THAT* I have a problem with.I don't consider these any different than our nightly snapshots or a different commercial build of an Apache project. In both of those cases, announcements about them or promoting them over the official project supplied releases is, IMO, not acceptable on the *users* list. I'm not promoting them over official project releases because there is no official project release, or nightly, that incorporates the fixes users have been asking for. This is a build Benjamin and I created to help users. I will not post anything on the user list, if as a PMC member you're telling me I can't. If you want to point a couple of your users at them to help test things or similar, fine as a lead up to 3.0.4. But they cannot be considered general available things similar to releases. Dan On Jul 27, 2011, at 10:48 AM, Jason van Zyl wrote: Maven PMC, Benjamin and I would like to make a distribution available that addresses several issues with the Apache Maven 3.0.3 release. We have pushed back all bugfixes that do not involve Eclipse Aether[a] and Eclipse Sisu[b] as their incorporation into the mainline and an official release is your decision. We haven't pushed any individual artifacts to Maven Central as part of creating the distribution, we have only created the distribution itself. If there is anything you want changed let us know and we'll change it, but we wanted to make these fixes available in a build for users who are having problems. We're not trying to represent it as anything other then a distribution that incorporates fixes users need. The build is available here: http://people.apache.org/~jvanzyl Summary of the issues Fixes pushed back to the ASF: [MNG-5064][1] mvn -nsu (--no-snapshot-updates) should not download snapshots (and break local builds) [MNG-5131][2] Wrong encoding for encrypted passwords [MNG-5113][3] NullPointerException on javadoc site generation [MNG-5137][4] Reactor resolution does not work for forked multi module builds [MNG-5096][5] exclusion on dependency with typetest-jar/type doesn't work in maven 3 [MNG-5135][6] Regression: in some cases aggregator mojo is unable to resolve dependencies with custom packaging Fixes not pushed back to the ASF as these are dependent on fixes in Eclipse Aether and Eclipse Sisu: [MNG-5042][7] Regression: CloningClassLoader causes StackOverflowError in groovy [MNG-5056][8] Test dependencies get packaged into WAR file. [MNG-5084][9] Resolver for plugins failing [MNG-5087][10] Maven 3 dependency resolution fails until maven-metadata-local.xml files (created by maven-invoker-plugin) are deleted [MNG-5125] [11]Regression: mvn 3.0.3 is extreemly slow with a large number of dependencies [MNG-5138][12] Dependency conflicts are extremely opaque [1]: http://jira.codehaus.org/browse/MNG-5064 [2]: http://jira.codehaus.org/browse/MNG-5131 [3]: http://jira.codehaus.org/browse/MNG-5113 [4]: http://jira.codehaus.org/browse/MNG-5137 [5]: http://jira.codehaus.org/browse/MNG-5096 [6]: http://jira.codehaus.org/browse/MNG-5135 [7]: http://jira.codehaus.org/browse/MNG-5042 [8]: http://jira.codehaus.org/browse/MNG-5056 [9]: http://jira.codehaus.org/browse/MNG-5084 [10]: http://jira.codehaus.org/browse/MNG-5087 [11]: http://jira.codehaus.org/browse/MNG-5125 [12]: http://jira.codehaus.org/browse/MNG-5138 [a]: http://eclipse.org/proposals/technology.aether/ [b]: http://eclipse.org/proposals/technology.sisu/ Thanks, Jason -- Jason van Zyl Eclipse Board Member Founder, Apache Maven http://twitter.com/jvanzyl - If I find ten thousand ways something won't work, I haven't failed. I am not discouraged, because every wrong attempt discarded is just one more step forward. -- Thomas Edison Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl - Our achievements speak for themselves. What we have to keep track of are our failures, discouragements and doubts. We tend to forget the past difficulties, the many false starts, and the painful groping. We see our past achievements as the end result of a clean forward thrust, and our present difficulties as signs of decline and decay. -- Eric Hoffer, Reflections on the Human Condition -- Daniel Kulp dk...@apache.org http://dankulp.com/blog Talend - http://www.talend.com
Re: Apache Maven distribution with fixes
Mark, No we cannot fork back. It is too large of a body of code to absorb without a grant, AL or no AL. I'm always happy to be proved stupid by consultation with legal. Until then, however, the policy seems perfectly clear to me. Only small amounts of code can be absorbed without a grant. --benson On Thu, Jul 28, 2011 at 8:52 AM, Mark Struberg strub...@yahoo.de wrote: Humm, guess there are only 3 options left in this case 1.) We wait 7 weeks or whatever time it takes (most probably it _will_ take more) 2.) You ship an ALv2 licensed version of Aether and Sisu which we can incorporate into an upcoming maven-3.0.4. 3.) We fork the last ALv2 licensed Aether version back to the Maven project and fix the bugs ourself. LieGrue, strub --- On Thu, 7/28/11, Jason van Zyl ja...@sonatype.com wrote: From: Jason van Zyl ja...@sonatype.com Subject: Re: Apache Maven distribution with fixes To: Maven Developers List dev@maven.apache.org Date: Thursday, July 28, 2011, 12:32 PM On Jul 28, 2011, at 8:25 AM, Mark Struberg wrote: mom jason. Before we ship 3.0.4 I'd like to fix the SCM URL postfix problem which exists in lots of DSCMs. Will do this in the next week. You probably have 6-7 weeks before an official 3.0.4 release would be made so you have plenty of time. If you are going to wait for Aether and Sisu to be provisioned at Eclipse then the total time for both of those to pass into that state is about 7 weeks. The build I proposed could not be an official release until such a time because there are fixes which rely on Sisu and Aether which are important for users. LieGrue, strub --- On Thu, 7/28/11, Jason van Zyl ja...@sonatype.com wrote: From: Jason van Zyl ja...@sonatype.com Subject: Re: Apache Maven distribution with fixes To: Maven Developers List dev@maven.apache.org Date: Thursday, July 28, 2011, 11:41 AM I'll assume that this is fine and no one objects. I'll announce this on the user list later today. On Jul 27, 2011, at 10:48 AM, Jason van Zyl wrote: Maven PMC, Benjamin and I would like to make a distribution available that addresses several issues with the Apache Maven 3.0.3 release. We have pushed back all bugfixes that do not involve Eclipse Aether[a] and Eclipse Sisu[b] as their incorporation into the mainline and an official release is your decision. We haven't pushed any individual artifacts to Maven Central as part of creating the distribution, we have only created the distribution itself. If there is anything you want changed let us know and we'll change it, but we wanted to make these fixes available in a build for users who are having problems. We're not trying to represent it as anything other then a distribution that incorporates fixes users need. The build is available here: http://people.apache.org/~jvanzyl Summary of the issues Fixes pushed back to the ASF: [MNG-5064][1] mvn -nsu (--no-snapshot-updates) should not download snapshots (and break local builds) [MNG-5131][2] Wrong encoding for encrypted passwords [MNG-5113][3] NullPointerException on javadoc site generation [MNG-5137][4] Reactor resolution does not work for forked multi module builds [MNG-5096][5] exclusion on dependency with typetest-jar/type doesn't work in maven 3 [MNG-5135][6] Regression: in some cases aggregator mojo is unable to resolve dependencies with custom packaging Fixes not pushed back to the ASF as these are dependent on fixes in Eclipse Aether and Eclipse Sisu: [MNG-5042][7] Regression: CloningClassLoader causes StackOverflowError in groovy [MNG-5056][8] Test dependencies get packaged into WAR file. [MNG-5084][9] Resolver for plugins failing [MNG-5087][10] Maven 3 dependency resolution fails until maven-metadata-local.xml files (created by maven-invoker-plugin) are deleted [MNG-5125] [11]Regression: mvn 3.0.3 is extreemly slow with a large number of dependencies [MNG-5138][12] Dependency conflicts are extremely opaque [1]: http://jira.codehaus.org/browse/MNG-5064 [2]: http://jira.codehaus.org/browse/MNG-5131 [3]: http://jira.codehaus.org/browse/MNG-5113 [4]: http://jira.codehaus.org/browse/MNG-5137 [5]: http://jira.codehaus.org/browse/MNG-5096 [6]: http://jira.codehaus.org/browse/MNG-5135 [7]: http://jira.codehaus.org/browse/MNG-5042 [8]: http://jira.codehaus.org/browse/MNG-5056 [9]: http://jira.codehaus.org/browse/MNG-5084 [10]: http://jira.codehaus.org/browse/MNG-5087 [11]: http://jira.codehaus.org/browse/MNG-5125 [12]: http://jira.codehaus.org/browse/MNG-5138 [a]: http://eclipse.org/proposals/technology.aether/ [b]: http://eclipse.org/proposals/technology.sisu/ Thanks, Jason -- Jason van Zyl Eclipse Board Member
Re: Apache Maven distribution with fixes
Benson, you are wrong. The answer to this question is really not clear and depends on a much more then just the pure amount of code. There are lots of discussions around that lately on legal and we have lots of detailed if/whens. If we have the history, then we can do the check. Gladly github provides those. Also there is still the option to fork it over to apache-extras and fix it there. LieGrue, strub --- On Thu, 7/28/11, Benson Margulies bimargul...@gmail.com wrote: From: Benson Margulies bimargul...@gmail.com Subject: Re: Apache Maven distribution with fixes To: Maven Developers List dev@maven.apache.org Date: Thursday, July 28, 2011, 1:06 PM Mark, No we cannot fork back. It is too large of a body of code to absorb without a grant, AL or no AL. I'm always happy to be proved stupid by consultation with legal. Until then, however, the policy seems perfectly clear to me. Only small amounts of code can be absorbed without a grant. --benson On Thu, Jul 28, 2011 at 8:52 AM, Mark Struberg strub...@yahoo.de wrote: Humm, guess there are only 3 options left in this case 1.) We wait 7 weeks or whatever time it takes (most probably it _will_ take more) 2.) You ship an ALv2 licensed version of Aether and Sisu which we can incorporate into an upcoming maven-3.0.4. 3.) We fork the last ALv2 licensed Aether version back to the Maven project and fix the bugs ourself. LieGrue, strub --- On Thu, 7/28/11, Jason van Zyl ja...@sonatype.com wrote: From: Jason van Zyl ja...@sonatype.com Subject: Re: Apache Maven distribution with fixes To: Maven Developers List dev@maven.apache.org Date: Thursday, July 28, 2011, 12:32 PM On Jul 28, 2011, at 8:25 AM, Mark Struberg wrote: mom jason. Before we ship 3.0.4 I'd like to fix the SCM URL postfix problem which exists in lots of DSCMs. Will do this in the next week. You probably have 6-7 weeks before an official 3.0.4 release would be made so you have plenty of time. If you are going to wait for Aether and Sisu to be provisioned at Eclipse then the total time for both of those to pass into that state is about 7 weeks. The build I proposed could not be an official release until such a time because there are fixes which rely on Sisu and Aether which are important for users. LieGrue, strub --- On Thu, 7/28/11, Jason van Zyl ja...@sonatype.com wrote: From: Jason van Zyl ja...@sonatype.com Subject: Re: Apache Maven distribution with fixes To: Maven Developers List dev@maven.apache.org Date: Thursday, July 28, 2011, 11:41 AM I'll assume that this is fine and no one objects. I'll announce this on the user list later today. On Jul 27, 2011, at 10:48 AM, Jason van Zyl wrote: Maven PMC, Benjamin and I would like to make a distribution available that addresses several issues with the Apache Maven 3.0.3 release. We have pushed back all bugfixes that do not involve Eclipse Aether[a] and Eclipse Sisu[b] as their incorporation into the mainline and an official release is your decision. We haven't pushed any individual artifacts to Maven Central as part of creating the distribution, we have only created the distribution itself. If there is anything you want changed let us know and we'll change it, but we wanted to make these fixes available in a build for users who are having problems. We're not trying to represent it as anything other then a distribution that incorporates fixes users need. The build is available here: http://people.apache.org/~jvanzyl Summary of the issues Fixes pushed back to the ASF: [MNG-5064][1] mvn -nsu (--no-snapshot-updates) should not download snapshots (and break local builds) [MNG-5131][2] Wrong encoding for encrypted passwords [MNG-5113][3] NullPointerException on javadoc site generation [MNG-5137][4] Reactor resolution does not work for forked multi module builds [MNG-5096][5] exclusion on dependency with typetest-jar/type doesn't work in maven 3 [MNG-5135][6] Regression: in some cases aggregator mojo is unable to resolve dependencies with custom packaging Fixes not pushed back to the ASF as these are dependent on fixes in Eclipse Aether and Eclipse Sisu: [MNG-5042][7] Regression: CloningClassLoader causes StackOverflowError in groovy [MNG-5056][8] Test dependencies get packaged into WAR file. [MNG-5084][9] Resolver for plugins failing [MNG-5087][10] Maven 3 dependency resolution fails until maven-metadata-local.xml files (created by maven-invoker-plugin) are deleted [MNG-5125] [11]Regression: mvn 3.0.3 is extreemly slow with a large number of dependencies [MNG-5138][12
Re: Apache Maven distribution with fixes
On Thursday, July 28, 2011 8:59:09 AM Jason van Zyl wrote: On Jul 28, 2011, at 8:49 AM, Daniel Kulp wrote: On Thursday, July 28, 2011 7:41:16 AM Jason van Zyl wrote: I'll assume that this is fine and no one objects. I'll announce this on the user list later today. *THAT* I have a problem with.I don't consider these any different than our nightly snapshots or a different commercial build of an Apache project. In both of those cases, announcements about them or promoting them over the official project supplied releases is, IMO, not acceptable on the *users* list. I'm not promoting them over official project releases because there is no official project release, or nightly, that incorporates the fixes users have been asking for. This is a build Benjamin and I created to help users. I will not post anything on the user list, if as a PMC member you're telling me I can't. I'm saying you can't make a general announcement about it as it would be no different than making announcements of commercial versions of projects (that contain things like fixes and features not available from Apache builds) on other projects users lists. The fact that builds are specifically labeled sonatype really emphasizes the commercial nature of these builds. In this particular case, if a specific user asks a question or has an issue, in a reply to that user, you can mention it, but make clear in the response: 1) There are non-sanctioned builds of Maven not endorsed by the Maven project. 2) It contains code and fixes that have not been incorporated into Apache Maven, not even to trunk. 3) As such, any fixes (or new bugs) may not be present in a future version of Maven. 4) They are using such builds at their own risk. 5) Due to the above, it's not recommend to use these builds in any sort of production scenario. At the end of the day, if you really cared about the Maven users, you'd help us get an official Apache version of 3.0.4 out. The fact that you are unwilling to do what is necessary to make that happen is very frustrating to me. Dan If you want to point a couple of your users at them to help test things or similar, fine as a lead up to 3.0.4. But they cannot be considered general available things similar to releases. Dan On Jul 27, 2011, at 10:48 AM, Jason van Zyl wrote: Maven PMC, Benjamin and I would like to make a distribution available that addresses several issues with the Apache Maven 3.0.3 release. We have pushed back all bugfixes that do not involve Eclipse Aether[a] and Eclipse Sisu[b] as their incorporation into the mainline and an official release is your decision. We haven't pushed any individual artifacts to Maven Central as part of creating the distribution, we have only created the distribution itself. If there is anything you want changed let us know and we'll change it, but we wanted to make these fixes available in a build for users who are having problems. We're not trying to represent it as anything other then a distribution that incorporates fixes users need. The build is available here: http://people.apache.org/~jvanzyl Summary of the issues Fixes pushed back to the ASF: [MNG-5064][1] mvn -nsu (--no-snapshot-updates) should not download snapshots (and break local builds) [MNG-5131][2] Wrong encoding for encrypted passwords [MNG-5113][3] NullPointerException on javadoc site generation [MNG-5137][4] Reactor resolution does not work for forked multi module builds [MNG-5096][5] exclusion on dependency with typetest-jar/type doesn't work in maven 3 [MNG-5135][6] Regression: in some cases aggregator mojo is unable to resolve dependencies with custom packaging Fixes not pushed back to the ASF as these are dependent on fixes in Eclipse Aether and Eclipse Sisu: [MNG-5042][7] Regression: CloningClassLoader causes StackOverflowError in groovy [MNG-5056][8] Test dependencies get packaged into WAR file. [MNG-5084][9] Resolver for plugins failing [MNG-5087][10] Maven 3 dependency resolution fails until maven-metadata-local.xml files (created by maven-invoker-plugin) are deleted [MNG-5125] [11]Regression: mvn 3.0.3 is extreemly slow with a large number of dependencies [MNG-5138][12] Dependency conflicts are extremely opaque [1]: http://jira.codehaus.org/browse/MNG-5064 [2]: http://jira.codehaus.org/browse/MNG-5131 [3]: http://jira.codehaus.org/browse/MNG-5113 [4]: http://jira.codehaus.org/browse/MNG-5137 [5]: http://jira.codehaus.org/browse/MNG-5096 [6]: http://jira.codehaus.org/browse/MNG-5135 [7]: http://jira.codehaus.org/browse/MNG-5042 [8]: http://jira.codehaus.org/browse/MNG-5056 [9]: http://jira.codehaus.org/browse/MNG-5084 [10]: http://jira.codehaus.org/browse/MNG-5087 [11]: http://jira.codehaus.org/browse/MNG-5125
Re: Apache Maven distribution with fixes
On Thu, Jul 28, 2011 at 9:10 AM, Mark Struberg strub...@yahoo.de wrote: Benson, you are wrong. The answer to this question is really not clear and depends on a much more then just the pure amount of code. There are lots of discussions around that lately on legal and we have lots of detailed if/whens. If we have the history, then we can do the check. Gladly github provides those. Also there is still the option to fork it over to apache-extras and fix it there. Mark, It seems to me that the net of your paragraph is to support my argument. If the committers slapped an AL dual license on Aether today, we could not just grab that code, with no further discussion, examination, and clearance, and fork it back into Apache. I spend a lot of time in the incubator, and the IP clearance policies have been hashed on this subject very recently. A podling I'm trying to launch has been told, in no uncertain terms, more or less what I wrote, by the lead legal advisor. Sure, if some of the code of some version of AEther was at ASF originally, that code could be teased out and brought back. But that's very different from 'oh, a dual license, we can grab it instantly.' Want to send some thread references? --benson LieGrue, strub --- On Thu, 7/28/11, Benson Margulies bimargul...@gmail.com wrote: From: Benson Margulies bimargul...@gmail.com Subject: Re: Apache Maven distribution with fixes To: Maven Developers List dev@maven.apache.org Date: Thursday, July 28, 2011, 1:06 PM Mark, No we cannot fork back. It is too large of a body of code to absorb without a grant, AL or no AL. I'm always happy to be proved stupid by consultation with legal. Until then, however, the policy seems perfectly clear to me. Only small amounts of code can be absorbed without a grant. --benson On Thu, Jul 28, 2011 at 8:52 AM, Mark Struberg strub...@yahoo.de wrote: Humm, guess there are only 3 options left in this case 1.) We wait 7 weeks or whatever time it takes (most probably it _will_ take more) 2.) You ship an ALv2 licensed version of Aether and Sisu which we can incorporate into an upcoming maven-3.0.4. 3.) We fork the last ALv2 licensed Aether version back to the Maven project and fix the bugs ourself. LieGrue, strub --- On Thu, 7/28/11, Jason van Zyl ja...@sonatype.com wrote: From: Jason van Zyl ja...@sonatype.com Subject: Re: Apache Maven distribution with fixes To: Maven Developers List dev@maven.apache.org Date: Thursday, July 28, 2011, 12:32 PM On Jul 28, 2011, at 8:25 AM, Mark Struberg wrote: mom jason. Before we ship 3.0.4 I'd like to fix the SCM URL postfix problem which exists in lots of DSCMs. Will do this in the next week. You probably have 6-7 weeks before an official 3.0.4 release would be made so you have plenty of time. If you are going to wait for Aether and Sisu to be provisioned at Eclipse then the total time for both of those to pass into that state is about 7 weeks. The build I proposed could not be an official release until such a time because there are fixes which rely on Sisu and Aether which are important for users. LieGrue, strub --- On Thu, 7/28/11, Jason van Zyl ja...@sonatype.com wrote: From: Jason van Zyl ja...@sonatype.com Subject: Re: Apache Maven distribution with fixes To: Maven Developers List dev@maven.apache.org Date: Thursday, July 28, 2011, 11:41 AM I'll assume that this is fine and no one objects. I'll announce this on the user list later today. On Jul 27, 2011, at 10:48 AM, Jason van Zyl wrote: Maven PMC, Benjamin and I would like to make a distribution available that addresses several issues with the Apache Maven 3.0.3 release. We have pushed back all bugfixes that do not involve Eclipse Aether[a] and Eclipse Sisu[b] as their incorporation into the mainline and an official release is your decision. We haven't pushed any individual artifacts to Maven Central as part of creating the distribution, we have only created the distribution itself. If there is anything you want changed let us know and we'll change it, but we wanted to make these fixes available in a build for users who are having problems. We're not trying to represent it as anything other then a distribution that incorporates fixes users need. The build is available here: http://people.apache.org/~jvanzyl Summary of the issues Fixes pushed back to the ASF: [MNG-5064][1] mvn -nsu (--no-snapshot-updates) should not download snapshots (and break local builds) [MNG-5131][2] Wrong encoding for encrypted passwords [MNG-5113][3] NullPointerException on javadoc site generation [MNG-5137][4] Reactor resolution does not work for forked multi
Re: Apache Maven distribution with fixes
On Jul 28, 2011, at 8:52 AM, Mark Struberg wrote: Humm, guess there are only 3 options left in this case 1.) We wait 7 weeks or whatever time it takes (most probably it _will_ take more) Not likely, it will probably be shorter as I was being conservative. The scheduling at Eclipse is like a clockwork. Once the review period of over the creation review is immediately scheduled. The creation review and initial legal review will have no issues because nearly 100% of the code was written by Sonatype employees and we're all cleared at Eclipse. The code will start the parallel IP immediately and probably clear IP review very fast given it's all Sonatype code and there is already precedent for a lot of our code going into Eclipse. 2.) You ship an ALv2 licensed version of Aether and Sisu which we can incorporate into an upcoming maven-3.0.4. The proposals are posted, I'm not changing the licenses now. 3.) We fork the last ALv2 licensed Aether version back to the Maven project and fix the bugs ourself. I believe this will never happen and you will put the project in a very bad place if you attempt to do that. Since our last release not a single Maven committer outside of Sonatype has made any bug fixes or patches to the core (Paul made one small feature addition). You guys are talking about a new wagon, POM5 formats, new logging, artifact lookup indirection, but the day to day of actually patching and bug fixing is entirely absent and things like the plugin ITs are failing day after day in CI. Looking at the situation empirically, the probability that you will have the time and energy to try and patch Aether and Sisu given no one has patched any of the normal core code here I find a highly impractical and dangerous proposal. Path 1) doesn't preclude your participation and we've done nothing to hinder Kristian or Herve from participating. LieGrue, strub --- On Thu, 7/28/11, Jason van Zyl ja...@sonatype.com wrote: From: Jason van Zyl ja...@sonatype.com Subject: Re: Apache Maven distribution with fixes To: Maven Developers List dev@maven.apache.org Date: Thursday, July 28, 2011, 12:32 PM On Jul 28, 2011, at 8:25 AM, Mark Struberg wrote: mom jason. Before we ship 3.0.4 I'd like to fix the SCM URL postfix problem which exists in lots of DSCMs. Will do this in the next week. You probably have 6-7 weeks before an official 3.0.4 release would be made so you have plenty of time. If you are going to wait for Aether and Sisu to be provisioned at Eclipse then the total time for both of those to pass into that state is about 7 weeks. The build I proposed could not be an official release until such a time because there are fixes which rely on Sisu and Aether which are important for users. LieGrue, strub --- On Thu, 7/28/11, Jason van Zyl ja...@sonatype.com wrote: From: Jason van Zyl ja...@sonatype.com Subject: Re: Apache Maven distribution with fixes To: Maven Developers List dev@maven.apache.org Date: Thursday, July 28, 2011, 11:41 AM I'll assume that this is fine and no one objects. I'll announce this on the user list later today. On Jul 27, 2011, at 10:48 AM, Jason van Zyl wrote: Maven PMC, Benjamin and I would like to make a distribution available that addresses several issues with the Apache Maven 3.0.3 release. We have pushed back all bugfixes that do not involve Eclipse Aether[a] and Eclipse Sisu[b] as their incorporation into the mainline and an official release is your decision. We haven't pushed any individual artifacts to Maven Central as part of creating the distribution, we have only created the distribution itself. If there is anything you want changed let us know and we'll change it, but we wanted to make these fixes available in a build for users who are having problems. We're not trying to represent it as anything other then a distribution that incorporates fixes users need. The build is available here: http://people.apache.org/~jvanzyl Summary of the issues Fixes pushed back to the ASF: [MNG-5064][1] mvn -nsu (--no-snapshot-updates) should not download snapshots (and break local builds) [MNG-5131][2] Wrong encoding for encrypted passwords [MNG-5113][3] NullPointerException on javadoc site generation [MNG-5137][4] Reactor resolution does not work for forked multi module builds [MNG-5096][5] exclusion on dependency with typetest-jar/type doesn't work in maven 3 [MNG-5135][6] Regression: in some cases aggregator mojo is unable to resolve dependencies with custom packaging Fixes not pushed back to the ASF as these are dependent on fixes in Eclipse Aether and Eclipse Sisu: [MNG-5042][7] Regression: CloningClassLoader causes StackOverflowError in groovy [MNG-5056][8] Test dependencies get packaged into WAR file. [MNG-5084][9] Resolver for plugins failing
Re: Apache Maven distribution with fixes
Correct me if I'm wrong, but it's not okay to even call the binary maven-XXX or apache-maven-XXX (unless it's a snapshot) at all without getting a PMC vote. I thought there were rules in our ASF release protocols about that. On 7/28/11 9:18 AM, Daniel Kulp wrote: On Thursday, July 28, 2011 8:59:09 AM Jason van Zyl wrote: On Jul 28, 2011, at 8:49 AM, Daniel Kulp wrote: On Thursday, July 28, 2011 7:41:16 AM Jason van Zyl wrote: I'll assume that this is fine and no one objects. I'll announce this on the user list later today. *THAT* I have a problem with.I don't consider these any different than our nightly snapshots or a different commercial build of an Apache project. In both of those cases, announcements about them or promoting them over the official project supplied releases is, IMO, not acceptable on the *users* list. I'm not promoting them over official project releases because there is no official project release, or nightly, that incorporates the fixes users have been asking for. This is a build Benjamin and I created to help users. I will not post anything on the user list, if as a PMC member you're telling me I can't. I'm saying you can't make a general announcement about it as it would be no different than making announcements of commercial versions of projects (that contain things like fixes and features not available from Apache builds) on other projects users lists. The fact that builds are specifically labeled sonatype really emphasizes the commercial nature of these builds. In this particular case, if a specific user asks a question or has an issue, in a reply to that user, you can mention it, but make clear in the response: 1) There are non-sanctioned builds of Maven not endorsed by the Maven project. 2) It contains code and fixes that have not been incorporated into Apache Maven, not even to trunk. 3) As such, any fixes (or new bugs) may not be present in a future version of Maven. 4) They are using such builds at their own risk. 5) Due to the above, it's not recommend to use these builds in any sort of production scenario. At the end of the day, if you really cared about the Maven users, you'd help us get an official Apache version of 3.0.4 out. The fact that you are unwilling to do what is necessary to make that happen is very frustrating to me. Dan If you want to point a couple of your users at them to help test things or similar, fine as a lead up to 3.0.4. But they cannot be considered general available things similar to releases. Dan On Jul 27, 2011, at 10:48 AM, Jason van Zyl wrote: Maven PMC, Benjamin and I would like to make a distribution available that addresses several issues with the Apache Maven 3.0.3 release. We have pushed back all bugfixes that do not involve Eclipse Aether[a] and Eclipse Sisu[b] as their incorporation into the mainline and an official release is your decision. We haven't pushed any individual artifacts to Maven Central as part of creating the distribution, we have only created the distribution itself. If there is anything you want changed let us know and we'll change it, but we wanted to make these fixes available in a build for users who are having problems. We're not trying to represent it as anything other then a distribution that incorporates fixes users need. The build is available here: http://people.apache.org/~jvanzyl Summary of the issues Fixes pushed back to the ASF: [MNG-5064][1] mvn -nsu (--no-snapshot-updates) should not download snapshots (and break local builds) [MNG-5131][2] Wrong encoding for encrypted passwords [MNG-5113][3] NullPointerException on javadoc site generation [MNG-5137][4] Reactor resolution does not work for forked multi module builds [MNG-5096][5]exclusion ondependency with typetest-jar/type doesn't work in maven 3 [MNG-5135][6] Regression: in some cases aggregator mojo is unable to resolve dependencies with custom packaging Fixes not pushed back to the ASF as these are dependent on fixes in Eclipse Aether and Eclipse Sisu: [MNG-5042][7] Regression: CloningClassLoader causes StackOverflowError in groovy [MNG-5056][8] Test dependencies get packaged into WAR file. [MNG-5084][9] Resolver for plugins failing [MNG-5087][10] Maven 3 dependency resolution fails until maven-metadata-local.xml files (created by maven-invoker-plugin) are deleted [MNG-5125] [11]Regression: mvn 3.0.3 is extreemly slow with a large number of dependencies [MNG-5138][12] Dependency conflicts are extremely opaque [1]: http://jira.codehaus.org/browse/MNG-5064 [2]: http://jira.codehaus.org/browse/MNG-5131 [3]: http://jira.codehaus.org/browse/MNG-5113 [4]: http://jira.codehaus.org/browse/MNG-5137 [5]: http://jira.codehaus.org/browse/MNG-5096 [6]: http://jira.codehaus.org/browse/MNG-5135 [7]: http://jira.codehaus.org/browse/MNG-5042 [8]: http://jira.codehaus.org/browse/MNG-5056 [9]: http://jira.codehaus.org/browse/MNG-5084 [10]:
Re: Apache Maven distribution with fixes
On Jul 28, 2011, at 9:18 AM, Daniel Kulp wrote: On Thursday, July 28, 2011 8:59:09 AM Jason van Zyl wrote: On Jul 28, 2011, at 8:49 AM, Daniel Kulp wrote: On Thursday, July 28, 2011 7:41:16 AM Jason van Zyl wrote: I'll assume that this is fine and no one objects. I'll announce this on the user list later today. *THAT* I have a problem with.I don't consider these any different than our nightly snapshots or a different commercial build of an Apache project. In both of those cases, announcements about them or promoting them over the official project supplied releases is, IMO, not acceptable on the *users* list. I'm not promoting them over official project releases because there is no official project release, or nightly, that incorporates the fixes users have been asking for. This is a build Benjamin and I created to help users. I will not post anything on the user list, if as a PMC member you're telling me I can't. I'm saying you can't make a general announcement about it as it would be no different than making announcements of commercial versions of projects (that contain things like fixes and features not available from Apache builds) on other projects users lists. The fact that builds are specifically labeled sonatype really emphasizes the commercial nature of these builds. I'm honestly confused about how to label it which is why I asked. There's nothing commercial in the build, and we'll call it or label it however you like. I'm not particular worried about the names, I just want to get the build to users. In this particular case, if a specific user asks a question or has an issue, in a reply to that user, you can mention it, but make clear in the response: 1) There are non-sanctioned builds of Maven not endorsed by the Maven project. I think that was clear from my initial email. But if you have some text you want included I'm happy to include it. 2) It contains code and fixes that have not been incorporated into Apache Maven, not even to trunk. I think that was also clear from the email. 3) As such, any fixes (or new bugs) may not be present in a future version of Maven. Sure, I can add that explaining the Aether and Sisu situation. 4) They are using such builds at their own risk. Aren't they always? 5) Due to the above, it's not recommend to use these builds in any sort of production scenario. I'm not going to say that. I wouldn't build anything and offer it to users if I didn't think it was good. None of the above has anything to do with its production readiness. At the end of the day, if you really cared about the Maven users, you'd help us get an official Apache version of 3.0.4 out. The fact that you are unwilling to do what is necessary to make that happen is very frustrating to me. It's entirely within your control as a PMC member to accept the use of industry accept license from a world-class open source organization. I think personally and others from Sonatype have shown they care. We've done vast majority of work along the path of 3.x. Even with all the recent events we still just pushed back a slew of fixes across several code bases and produced a build because no one else here is stepping up to do any of the work necessary to keep the project going. Dan If you want to point a couple of your users at them to help test things or similar, fine as a lead up to 3.0.4. But they cannot be considered general available things similar to releases. Dan On Jul 27, 2011, at 10:48 AM, Jason van Zyl wrote: Maven PMC, Benjamin and I would like to make a distribution available that addresses several issues with the Apache Maven 3.0.3 release. We have pushed back all bugfixes that do not involve Eclipse Aether[a] and Eclipse Sisu[b] as their incorporation into the mainline and an official release is your decision. We haven't pushed any individual artifacts to Maven Central as part of creating the distribution, we have only created the distribution itself. If there is anything you want changed let us know and we'll change it, but we wanted to make these fixes available in a build for users who are having problems. We're not trying to represent it as anything other then a distribution that incorporates fixes users need. The build is available here: http://people.apache.org/~jvanzyl Summary of the issues Fixes pushed back to the ASF: [MNG-5064][1] mvn -nsu (--no-snapshot-updates) should not download snapshots (and break local builds) [MNG-5131][2] Wrong encoding for encrypted passwords [MNG-5113][3] NullPointerException on javadoc site generation [MNG-5137][4] Reactor resolution does not work for forked multi module builds [MNG-5096][5] exclusion on dependency with typetest-jar/type doesn't work in maven 3 [MNG-5135][6] Regression: in some cases aggregator mojo is unable
Re: Apache Maven distribution with fixes
We will rebuild it and call it whatever you guys want. I don't know what the rules are because they always seem to change, or what code has to be in a build to be called this or that. In this case we are just like anyone else in the community making a build to fix problems because there is nothing available officially. I'll call it whatever and then I'd like to tell people exactly what's in it, incorporate whatever you want us to say about it and then let users have it. On Jul 28, 2011, at 9:32 AM, John Casey wrote: Correct me if I'm wrong, but it's not okay to even call the binary maven-XXX or apache-maven-XXX (unless it's a snapshot) at all without getting a PMC vote. I thought there were rules in our ASF release protocols about that. On 7/28/11 9:18 AM, Daniel Kulp wrote: On Thursday, July 28, 2011 8:59:09 AM Jason van Zyl wrote: On Jul 28, 2011, at 8:49 AM, Daniel Kulp wrote: On Thursday, July 28, 2011 7:41:16 AM Jason van Zyl wrote: I'll assume that this is fine and no one objects. I'll announce this on the user list later today. *THAT* I have a problem with.I don't consider these any different than our nightly snapshots or a different commercial build of an Apache project. In both of those cases, announcements about them or promoting them over the official project supplied releases is, IMO, not acceptable on the *users* list. I'm not promoting them over official project releases because there is no official project release, or nightly, that incorporates the fixes users have been asking for. This is a build Benjamin and I created to help users. I will not post anything on the user list, if as a PMC member you're telling me I can't. I'm saying you can't make a general announcement about it as it would be no different than making announcements of commercial versions of projects (that contain things like fixes and features not available from Apache builds) on other projects users lists. The fact that builds are specifically labeled sonatype really emphasizes the commercial nature of these builds. In this particular case, if a specific user asks a question or has an issue, in a reply to that user, you can mention it, but make clear in the response: 1) There are non-sanctioned builds of Maven not endorsed by the Maven project. 2) It contains code and fixes that have not been incorporated into Apache Maven, not even to trunk. 3) As such, any fixes (or new bugs) may not be present in a future version of Maven. 4) They are using such builds at their own risk. 5) Due to the above, it's not recommend to use these builds in any sort of production scenario. At the end of the day, if you really cared about the Maven users, you'd help us get an official Apache version of 3.0.4 out. The fact that you are unwilling to do what is necessary to make that happen is very frustrating to me. Dan If you want to point a couple of your users at them to help test things or similar, fine as a lead up to 3.0.4. But they cannot be considered general available things similar to releases. Dan On Jul 27, 2011, at 10:48 AM, Jason van Zyl wrote: Maven PMC, Benjamin and I would like to make a distribution available that addresses several issues with the Apache Maven 3.0.3 release. We have pushed back all bugfixes that do not involve Eclipse Aether[a] and Eclipse Sisu[b] as their incorporation into the mainline and an official release is your decision. We haven't pushed any individual artifacts to Maven Central as part of creating the distribution, we have only created the distribution itself. If there is anything you want changed let us know and we'll change it, but we wanted to make these fixes available in a build for users who are having problems. We're not trying to represent it as anything other then a distribution that incorporates fixes users need. The build is available here: http://people.apache.org/~jvanzyl Summary of the issues Fixes pushed back to the ASF: [MNG-5064][1] mvn -nsu (--no-snapshot-updates) should not download snapshots (and break local builds) [MNG-5131][2] Wrong encoding for encrypted passwords [MNG-5113][3] NullPointerException on javadoc site generation [MNG-5137][4] Reactor resolution does not work for forked multi module builds [MNG-5096][5]exclusion ondependency with typetest-jar/type doesn't work in maven 3 [MNG-5135][6] Regression: in some cases aggregator mojo is unable to resolve dependencies with custom packaging Fixes not pushed back to the ASF as these are dependent on fixes in Eclipse Aether and Eclipse Sisu: [MNG-5042][7] Regression: CloningClassLoader causes StackOverflowError in groovy [MNG-5056][8] Test dependencies get packaged into WAR file. [MNG-5084][9] Resolver for plugins failing [MNG-5087][10] Maven 3 dependency resolution fails until
Re: Apache Maven distribution with fixes
On Thursday, July 28, 2011 9:32:07 AM John Casey wrote: Correct me if I'm wrong, but it's not okay to even call the binary maven-XXX or apache-maven-XXX (unless it's a snapshot) at all without getting a PMC vote. I thought there were rules in our ASF release protocols about that. That's actually a good point. In this case, the build contains stuff that is NOT part of any Apache Maven build, changes that are not in SVN, etc Thus, it's not Maven and cannot use those marks as part of the name.It can be Jason's build thingy based on Apache Maven, but not just Maven or Apache Maven. Also, as it is NOT a snapshot of code available in trunk/svn or part of the project, I also believe it's not something that can be distributed or promoted from Apache hardware or the Apache lists. Basically, it's not Maven and thus it cannot be treated as such. Dan On 7/28/11 9:18 AM, Daniel Kulp wrote: On Thursday, July 28, 2011 8:59:09 AM Jason van Zyl wrote: On Jul 28, 2011, at 8:49 AM, Daniel Kulp wrote: On Thursday, July 28, 2011 7:41:16 AM Jason van Zyl wrote: I'll assume that this is fine and no one objects. I'll announce this on the user list later today. *THAT* I have a problem with.I don't consider these any different than our nightly snapshots or a different commercial build of an Apache project. In both of those cases, announcements about them or promoting them over the official project supplied releases is, IMO, not acceptable on the *users* list. I'm not promoting them over official project releases because there is no official project release, or nightly, that incorporates the fixes users have been asking for. This is a build Benjamin and I created to help users. I will not post anything on the user list, if as a PMC member you're telling me I can't. I'm saying you can't make a general announcement about it as it would be no different than making announcements of commercial versions of projects (that contain things like fixes and features not available from Apache builds) on other projects users lists. The fact that builds are specifically labeled sonatype really emphasizes the commercial nature of these builds. In this particular case, if a specific user asks a question or has an issue, in a reply to that user, you can mention it, but make clear in the response: 1) There are non-sanctioned builds of Maven not endorsed by the Maven project. 2) It contains code and fixes that have not been incorporated into Apache Maven, not even to trunk. 3) As such, any fixes (or new bugs) may not be present in a future version of Maven. 4) They are using such builds at their own risk. 5) Due to the above, it's not recommend to use these builds in any sort of production scenario. At the end of the day, if you really cared about the Maven users, you'd help us get an official Apache version of 3.0.4 out. The fact that you are unwilling to do what is necessary to make that happen is very frustrating to me. Dan If you want to point a couple of your users at them to help test things or similar, fine as a lead up to 3.0.4. But they cannot be considered general available things similar to releases. Dan On Jul 27, 2011, at 10:48 AM, Jason van Zyl wrote: Maven PMC, Benjamin and I would like to make a distribution available that addresses several issues with the Apache Maven 3.0.3 release. We have pushed back all bugfixes that do not involve Eclipse Aether[a] and Eclipse Sisu[b] as their incorporation into the mainline and an official release is your decision. We haven't pushed any individual artifacts to Maven Central as part of creating the distribution, we have only created the distribution itself. If there is anything you want changed let us know and we'll change it, but we wanted to make these fixes available in a build for users who are having problems. We're not trying to represent it as anything other then a distribution that incorporates fixes users need. The build is available here: http://people.apache.org/~jvanzyl Summary of the issues Fixes pushed back to the ASF: [MNG-5064][1] mvn -nsu (--no-snapshot-updates) should not download snapshots (and break local builds) [MNG-5131][2] Wrong encoding for encrypted passwords [MNG-5113][3] NullPointerException on javadoc site generation [MNG-5137][4] Reactor resolution does not work for forked multi module builds [MNG-5096][5]exclusion ondependency with typetest-jar/type doesn't work in maven 3 [MNG-5135][6] Regression: in some cases aggregator mojo is unable to resolve dependencies with custom packaging Fixes not pushed back to the ASF as these are dependent on fixes in Eclipse Aether and Eclipse Sisu: [MNG-5042][7] Regression:
Re: Apache Maven distribution with fixes
On Jul 28, 2011, at 9:18 AM, Daniel Kulp wrote: At the end of the day, if you really cared about the Maven users, you'd help us get an official Apache version of 3.0.4 out. The fact that you are unwilling to do what is necessary to make that happen is very frustrating to me. How about you take the fixes we did push into SVN and do a 3.0.4 and then I can make another build with the rest of the fixes. Dan If you want to point a couple of your users at them to help test things or similar, fine as a lead up to 3.0.4. But they cannot be considered general available things similar to releases. Dan On Jul 27, 2011, at 10:48 AM, Jason van Zyl wrote: Maven PMC, Benjamin and I would like to make a distribution available that addresses several issues with the Apache Maven 3.0.3 release. We have pushed back all bugfixes that do not involve Eclipse Aether[a] and Eclipse Sisu[b] as their incorporation into the mainline and an official release is your decision. We haven't pushed any individual artifacts to Maven Central as part of creating the distribution, we have only created the distribution itself. If there is anything you want changed let us know and we'll change it, but we wanted to make these fixes available in a build for users who are having problems. We're not trying to represent it as anything other then a distribution that incorporates fixes users need. The build is available here: http://people.apache.org/~jvanzyl Summary of the issues Fixes pushed back to the ASF: [MNG-5064][1] mvn -nsu (--no-snapshot-updates) should not download snapshots (and break local builds) [MNG-5131][2] Wrong encoding for encrypted passwords [MNG-5113][3] NullPointerException on javadoc site generation [MNG-5137][4] Reactor resolution does not work for forked multi module builds [MNG-5096][5] exclusion on dependency with typetest-jar/type doesn't work in maven 3 [MNG-5135][6] Regression: in some cases aggregator mojo is unable to resolve dependencies with custom packaging Fixes not pushed back to the ASF as these are dependent on fixes in Eclipse Aether and Eclipse Sisu: [MNG-5042][7] Regression: CloningClassLoader causes StackOverflowError in groovy [MNG-5056][8] Test dependencies get packaged into WAR file. [MNG-5084][9] Resolver for plugins failing [MNG-5087][10] Maven 3 dependency resolution fails until maven-metadata-local.xml files (created by maven-invoker-plugin) are deleted [MNG-5125] [11]Regression: mvn 3.0.3 is extreemly slow with a large number of dependencies [MNG-5138][12] Dependency conflicts are extremely opaque [1]: http://jira.codehaus.org/browse/MNG-5064 [2]: http://jira.codehaus.org/browse/MNG-5131 [3]: http://jira.codehaus.org/browse/MNG-5113 [4]: http://jira.codehaus.org/browse/MNG-5137 [5]: http://jira.codehaus.org/browse/MNG-5096 [6]: http://jira.codehaus.org/browse/MNG-5135 [7]: http://jira.codehaus.org/browse/MNG-5042 [8]: http://jira.codehaus.org/browse/MNG-5056 [9]: http://jira.codehaus.org/browse/MNG-5084 [10]: http://jira.codehaus.org/browse/MNG-5087 [11]: http://jira.codehaus.org/browse/MNG-5125 [12]: http://jira.codehaus.org/browse/MNG-5138 [a]: http://eclipse.org/proposals/technology.aether/ [b]: http://eclipse.org/proposals/technology.sisu/ Thanks, Jason -- Jason van Zyl Eclipse Board Member Founder, Apache Maven http://twitter.com/jvanzyl - If I find ten thousand ways something won't work, I haven't failed. I am not discouraged, because every wrong attempt discarded is just one more step forward. -- Thomas Edison Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl - Our achievements speak for themselves. What we have to keep track of are our failures, discouragements and doubts. We tend to forget the past difficulties, the many false starts, and the painful groping. We see our past achievements as the end result of a clean forward thrust, and our present difficulties as signs of decline and decay. -- Eric Hoffer, Reflections on the Human Condition Thanks, Jason -- Jason van Zyl 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 -- Daniel Kulp dk...@apache.org http://dankulp.com/blog Talend - http://www.talend.com - To unsubscribe, e-mail:
Re: Apache Maven distribution with fixes
The reason why no one committed to Aether beside yourself is partly that it requires to sign some CLA which only unilaterally grants rights (as we can certainly see now!). Which is another reason why I consider a fork to apache-extras a good idea. And don't come me with the argument that the Maven community is not able to maintain Maven without your help. At least there IS now a CI environment. And remember who built the git stuff on which your whole company is based upon? The argument is not that we cannot fix it becaues we are dumb little bunnies, but because the code is not under our control anymore! LieGrue, strub --- On Thu, 7/28/11, Jason van Zyl ja...@sonatype.com wrote: From: Jason van Zyl ja...@sonatype.com Subject: Re: Apache Maven distribution with fixes To: Maven Developers List dev@maven.apache.org Date: Thursday, July 28, 2011, 1:23 PM On Jul 28, 2011, at 8:52 AM, Mark Struberg wrote: Humm, guess there are only 3 options left in this case 1.) We wait 7 weeks or whatever time it takes (most probably it _will_ take more) Not likely, it will probably be shorter as I was being conservative. The scheduling at Eclipse is like a clockwork. Once the review period of over the creation review is immediately scheduled. The creation review and initial legal review will have no issues because nearly 100% of the code was written by Sonatype employees and we're all cleared at Eclipse. The code will start the parallel IP immediately and probably clear IP review very fast given it's all Sonatype code and there is already precedent for a lot of our code going into Eclipse. 2.) You ship an ALv2 licensed version of Aether and Sisu which we can incorporate into an upcoming maven-3.0.4. The proposals are posted, I'm not changing the licenses now. 3.) We fork the last ALv2 licensed Aether version back to the Maven project and fix the bugs ourself. I believe this will never happen and you will put the project in a very bad place if you attempt to do that. Since our last release not a single Maven committer outside of Sonatype has made any bug fixes or patches to the core (Paul made one small feature addition). You guys are talking about a new wagon, POM5 formats, new logging, artifact lookup indirection, but the day to day of actually patching and bug fixing is entirely absent and things like the plugin ITs are failing day after day in CI. Looking at the situation empirically, the probability that you will have the time and energy to try and patch Aether and Sisu given no one has patched any of the normal core code here I find a highly impractical and dangerous proposal. Path 1) doesn't preclude your participation and we've done nothing to hinder Kristian or Herve from participating. LieGrue, strub --- On Thu, 7/28/11, Jason van Zyl ja...@sonatype.com wrote: From: Jason van Zyl ja...@sonatype.com Subject: Re: Apache Maven distribution with fixes To: Maven Developers List dev@maven.apache.org Date: Thursday, July 28, 2011, 12:32 PM On Jul 28, 2011, at 8:25 AM, Mark Struberg wrote: mom jason. Before we ship 3.0.4 I'd like to fix the SCM URL postfix problem which exists in lots of DSCMs. Will do this in the next week. You probably have 6-7 weeks before an official 3.0.4 release would be made so you have plenty of time. If you are going to wait for Aether and Sisu to be provisioned at Eclipse then the total time for both of those to pass into that state is about 7 weeks. The build I proposed could not be an official release until such a time because there are fixes which rely on Sisu and Aether which are important for users. LieGrue, strub --- On Thu, 7/28/11, Jason van Zyl ja...@sonatype.com wrote: From: Jason van Zyl ja...@sonatype.com Subject: Re: Apache Maven distribution with fixes To: Maven Developers List dev@maven.apache.org Date: Thursday, July 28, 2011, 11:41 AM I'll assume that this is fine and no one objects. I'll announce this on the user list later today. On Jul 27, 2011, at 10:48 AM, Jason van Zyl wrote: Maven PMC, Benjamin and I would like to make a distribution available that addresses several issues with the Apache Maven 3.0.3 release. We have pushed back all bugfixes that do not involve Eclipse Aether[a] and Eclipse Sisu[b] as their incorporation into the mainline and an official release is your decision. We haven't pushed any individual artifacts to Maven Central as part of creating the distribution, we have only created the distribution itself. If there is anything you want changed let us know and we'll change it, but we wanted to make these fixes available in a build for users who are having problems. We're not trying to represent it as anything other then a distribution that incorporates fixes users need. The build
Re: Apache Maven distribution with fixes
From my POV it could be a good thing for users to at least push a 3.0.4 release with what Benj fixed. If Mark is sure to be able to fix next week the bug he mentioned let's wait him. For Aether/Sisu and additional fixes and required dependencies I let others active dev/pmcs decide what they want. For me it's a without end conflict (at without good end for users and the community). cheers Arnaud On Thu, Jul 28, 2011 at 4:01 PM, Jason van Zyl ja...@sonatype.com wrote: On Jul 28, 2011, at 9:18 AM, Daniel Kulp wrote: At the end of the day, if you really cared about the Maven users, you'd help us get an official Apache version of 3.0.4 out. The fact that you are unwilling to do what is necessary to make that happen is very frustrating to me. How about you take the fixes we did push into SVN and do a 3.0.4 and then I can make another build with the rest of the fixes. Dan If you want to point a couple of your users at them to help test things or similar, fine as a lead up to 3.0.4. But they cannot be considered general available things similar to releases. Dan On Jul 27, 2011, at 10:48 AM, Jason van Zyl wrote: Maven PMC, Benjamin and I would like to make a distribution available that addresses several issues with the Apache Maven 3.0.3 release. We have pushed back all bugfixes that do not involve Eclipse Aether[a] and Eclipse Sisu[b] as their incorporation into the mainline and an official release is your decision. We haven't pushed any individual artifacts to Maven Central as part of creating the distribution, we have only created the distribution itself. If there is anything you want changed let us know and we'll change it, but we wanted to make these fixes available in a build for users who are having problems. We're not trying to represent it as anything other then a distribution that incorporates fixes users need. The build is available here: http://people.apache.org/~jvanzyl Summary of the issues Fixes pushed back to the ASF: [MNG-5064][1] mvn -nsu (--no-snapshot-updates) should not download snapshots (and break local builds) [MNG-5131][2] Wrong encoding for encrypted passwords [MNG-5113][3] NullPointerException on javadoc site generation [MNG-5137][4] Reactor resolution does not work for forked multi module builds [MNG-5096][5] exclusion on dependency with typetest-jar/type doesn't work in maven 3 [MNG-5135][6] Regression: in some cases aggregator mojo is unable to resolve dependencies with custom packaging Fixes not pushed back to the ASF as these are dependent on fixes in Eclipse Aether and Eclipse Sisu: [MNG-5042][7] Regression: CloningClassLoader causes StackOverflowError in groovy [MNG-5056][8] Test dependencies get packaged into WAR file. [MNG-5084][9] Resolver for plugins failing [MNG-5087][10] Maven 3 dependency resolution fails until maven-metadata-local.xml files (created by maven-invoker-plugin) are deleted [MNG-5125] [11]Regression: mvn 3.0.3 is extreemly slow with a large number of dependencies [MNG-5138][12] Dependency conflicts are extremely opaque [1]: http://jira.codehaus.org/browse/MNG-5064 [2]: http://jira.codehaus.org/browse/MNG-5131 [3]: http://jira.codehaus.org/browse/MNG-5113 [4]: http://jira.codehaus.org/browse/MNG-5137 [5]: http://jira.codehaus.org/browse/MNG-5096 [6]: http://jira.codehaus.org/browse/MNG-5135 [7]: http://jira.codehaus.org/browse/MNG-5042 [8]: http://jira.codehaus.org/browse/MNG-5056 [9]: http://jira.codehaus.org/browse/MNG-5084 [10]: http://jira.codehaus.org/browse/MNG-5087 [11]: http://jira.codehaus.org/browse/MNG-5125 [12]: http://jira.codehaus.org/browse/MNG-5138 [a]: http://eclipse.org/proposals/technology.aether/ [b]: http://eclipse.org/proposals/technology.sisu/ Thanks, Jason -- Jason van Zyl Eclipse Board Member Founder, Apache Maven http://twitter.com/jvanzyl - If I find ten thousand ways something won't work, I haven't failed. I am not discouraged, because every wrong attempt discarded is just one more step forward. -- Thomas Edison Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl - Our achievements speak for themselves. What we have to keep track of are our failures, discouragements and doubts. We tend to forget the past difficulties, the many false starts, and the painful groping. We see our past achievements as the end result of a clean forward thrust, and our present difficulties as signs of decline and decay. -- Eric Hoffer, Reflections on the Human Condition
Re: Apache Maven distribution with fixes
perfectly fine with me. LieGrue, strub --- On Thu, 7/28/11, Arnaud Héritier aherit...@gmail.com wrote: From: Arnaud Héritier aherit...@gmail.com Subject: Re: Apache Maven distribution with fixes To: Maven Developers List dev@maven.apache.org Date: Thursday, July 28, 2011, 2:27 PM From my POV it could be a good thing for users to at least push a 3.0.4 release with what Benj fixed. If Mark is sure to be able to fix next week the bug he mentioned let's wait him. For Aether/Sisu and additional fixes and required dependencies I let others active dev/pmcs decide what they want. For me it's a without end conflict (at without good end for users and the community). cheers Arnaud On Thu, Jul 28, 2011 at 4:01 PM, Jason van Zyl ja...@sonatype.com wrote: On Jul 28, 2011, at 9:18 AM, Daniel Kulp wrote: At the end of the day, if you really cared about the Maven users, you'd help us get an official Apache version of 3.0.4 out. The fact that you are unwilling to do what is necessary to make that happen is very frustrating to me. How about you take the fixes we did push into SVN and do a 3.0.4 and then I can make another build with the rest of the fixes. Dan If you want to point a couple of your users at them to help test things or similar, fine as a lead up to 3.0.4. But they cannot be considered general available things similar to releases. Dan On Jul 27, 2011, at 10:48 AM, Jason van Zyl wrote: Maven PMC, Benjamin and I would like to make a distribution available that addresses several issues with the Apache Maven 3.0.3 release. We have pushed back all bugfixes that do not involve Eclipse Aether[a] and Eclipse Sisu[b] as their incorporation into the mainline and an official release is your decision. We haven't pushed any individual artifacts to Maven Central as part of creating the distribution, we have only created the distribution itself. If there is anything you want changed let us know and we'll change it, but we wanted to make these fixes available in a build for users who are having problems. We're not trying to represent it as anything other then a distribution that incorporates fixes users need. The build is available here: http://people.apache.org/~jvanzyl Summary of the issues Fixes pushed back to the ASF: [MNG-5064][1] mvn -nsu (--no-snapshot-updates) should not download snapshots (and break local builds) [MNG-5131][2] Wrong encoding for encrypted passwords [MNG-5113][3] NullPointerException on javadoc site generation [MNG-5137][4] Reactor resolution does not work for forked multi module builds [MNG-5096][5] exclusion on dependency with typetest-jar/type doesn't work in maven 3 [MNG-5135][6] Regression: in some cases aggregator mojo is unable to resolve dependencies with custom packaging Fixes not pushed back to the ASF as these are dependent on fixes in Eclipse Aether and Eclipse Sisu: [MNG-5042][7] Regression: CloningClassLoader causes StackOverflowError in groovy [MNG-5056][8] Test dependencies get packaged into WAR file. [MNG-5084][9] Resolver for plugins failing [MNG-5087][10] Maven 3 dependency resolution fails until maven-metadata-local.xml files (created by maven-invoker-plugin) are deleted [MNG-5125] [11]Regression: mvn 3.0.3 is extreemly slow with a large number of dependencies [MNG-5138][12] Dependency conflicts are extremely opaque [1]: http://jira.codehaus.org/browse/MNG-5064 [2]: http://jira.codehaus.org/browse/MNG-5131 [3]: http://jira.codehaus.org/browse/MNG-5113 [4]: http://jira.codehaus.org/browse/MNG-5137 [5]: http://jira.codehaus.org/browse/MNG-5096 [6]: http://jira.codehaus.org/browse/MNG-5135 [7]: http://jira.codehaus.org/browse/MNG-5042 [8]: http://jira.codehaus.org/browse/MNG-5056 [9]: http://jira.codehaus.org/browse/MNG-5084 [10]: http://jira.codehaus.org/browse/MNG-5087 [11]: http://jira.codehaus.org/browse/MNG-5125 [12]: http://jira.codehaus.org/browse/MNG-5138 [a]: http://eclipse.org/proposals/technology.aether/ [b]: http://eclipse.org/proposals/technology.sisu/ Thanks, Jason -- Jason van Zyl Eclipse Board Member Founder, Apache Maven http://twitter.com/jvanzyl - If I find ten thousand ways something won't work, I haven't failed. I am not discouraged, because every wrong attempt discarded is just one more step forward. -- Thomas Edison Thanks, Jason -- Jason van Zyl Founder, Apache Maven http
Re: Apache Maven distribution with fixes
I think apache-extras would be the appropriate place, too. I understand that there are concerns about code grants, etc. but at the same time there are reasons to believe there would be practical limitations preventing us from maintaining the fixes we might need in aether or sisu...even leaving aside the CLA. The pace may not be what people outside of the project want, but at least if you're a committer, you have the option to contribute to the project in a constructive way. As opposed to just arriving on-stage a couple hours after a barrage of commits, with a binary in hand. On 7/28/11 10:23 AM, Mark Struberg wrote: The reason why no one committed to Aether beside yourself is partly that it requires to sign some CLA which only unilaterally grants rights (as we can certainly see now!). Which is another reason why I consider a fork to apache-extras a good idea. And don't come me with the argument that the Maven community is not able to maintain Maven without your help. At least there IS now a CI environment. And remember who built the git stuff on which your whole company is based upon? The argument is not that we cannot fix it becaues we are dumb little bunnies, but because the code is not under our control anymore! LieGrue, strub --- On Thu, 7/28/11, Jason van Zylja...@sonatype.com wrote: From: Jason van Zylja...@sonatype.com Subject: Re: Apache Maven distribution with fixes To: Maven Developers Listdev@maven.apache.org Date: Thursday, July 28, 2011, 1:23 PM On Jul 28, 2011, at 8:52 AM, Mark Struberg wrote: Humm, guess there are only 3 options left in this case 1.) We wait 7 weeks or whatever time it takes (most probably it _will_ take more) Not likely, it will probably be shorter as I was being conservative. The scheduling at Eclipse is like a clockwork. Once the review period of over the creation review is immediately scheduled. The creation review and initial legal review will have no issues because nearly 100% of the code was written by Sonatype employees and we're all cleared at Eclipse. The code will start the parallel IP immediately and probably clear IP review very fast given it's all Sonatype code and there is already precedent for a lot of our code going into Eclipse. 2.) You ship an ALv2 licensed version of Aether and Sisu which we can incorporate into an upcoming maven-3.0.4. The proposals are posted, I'm not changing the licenses now. 3.) We fork the last ALv2 licensed Aether version back to the Maven project and fix the bugs ourself. I believe this will never happen and you will put the project in a very bad place if you attempt to do that. Since our last release not a single Maven committer outside of Sonatype has made any bug fixes or patches to the core (Paul made one small feature addition). You guys are talking about a new wagon, POM5 formats, new logging, artifact lookup indirection, but the day to day of actually patching and bug fixing is entirely absent and things like the plugin ITs are failing day after day in CI. Looking at the situation empirically, the probability that you will have the time and energy to try and patch Aether and Sisu given no one has patched any of the normal core code here I find a highly impractical and dangerous proposal. Path 1) doesn't preclude your participation and we've done nothing to hinder Kristian or Herve from participating. LieGrue, strub --- On Thu, 7/28/11, Jason van Zylja...@sonatype.com wrote: From: Jason van Zylja...@sonatype.com Subject: Re: Apache Maven distribution with fixes To: Maven Developers Listdev@maven.apache.org Date: Thursday, July 28, 2011, 12:32 PM On Jul 28, 2011, at 8:25 AM, Mark Struberg wrote: mom jason. Before we ship 3.0.4 I'd like to fix the SCM URL postfix problem which exists in lots of DSCMs. Will do this in the next week. You probably have 6-7 weeks before an official 3.0.4 release would be made so you have plenty of time. If you are going to wait for Aether and Sisu to be provisioned at Eclipse then the total time for both of those to pass into that state is about 7 weeks. The build I proposed could not be an official release until such a time because there are fixes which rely on Sisu and Aether which are important for users. LieGrue, strub --- On Thu, 7/28/11, Jason van Zylja...@sonatype.com wrote: From: Jason van Zylja...@sonatype.com Subject: Re: Apache Maven distribution with fixes To: Maven Developers Listdev@maven.apache.org Date: Thursday, July 28, 2011, 11:41 AM I'll assume that this is fine and no one objects. I'll announce this on the user list later today. On Jul 27, 2011, at 10:48 AM, Jason van Zyl wrote: Maven PMC, Benjamin and I would like to make a distribution available that addresses several issues with the Apache Maven 3.0.3 release. We have pushed back all bugfixes that do not involve Eclipse Aether[a] and Eclipse Sisu[b] as their incorporation into the mainline and an official
Re: Apache Maven distribution with fixes
+1 Can bentmann's fixes be applied without adopting the updated version of Aether? On 7/28/11 10:27 AM, Arnaud Héritier wrote: From my POV it could be a good thing for users to at least push a 3.0.4 release with what Benj fixed. If Mark is sure to be able to fix next week the bug he mentioned let's wait him. For Aether/Sisu and additional fixes and required dependencies I let others active dev/pmcs decide what they want. For me it's a without end conflict (at without good end for users and the community). cheers Arnaud On Thu, Jul 28, 2011 at 4:01 PM, Jason van Zylja...@sonatype.com wrote: On Jul 28, 2011, at 9:18 AM, Daniel Kulp wrote: At the end of the day, if you really cared about the Maven users, you'd help us get an official Apache version of 3.0.4 out. The fact that you are unwilling to do what is necessary to make that happen is very frustrating to me. How about you take the fixes we did push into SVN and do a 3.0.4 and then I can make another build with the rest of the fixes. Dan If you want to point a couple of your users at them to help test things or similar, fine as a lead up to 3.0.4. But they cannot be considered general available things similar to releases. Dan On Jul 27, 2011, at 10:48 AM, Jason van Zyl wrote: Maven PMC, Benjamin and I would like to make a distribution available that addresses several issues with the Apache Maven 3.0.3 release. We have pushed back all bugfixes that do not involve Eclipse Aether[a] and Eclipse Sisu[b] as their incorporation into the mainline and an official release is your decision. We haven't pushed any individual artifacts to Maven Central as part of creating the distribution, we have only created the distribution itself. If there is anything you want changed let us know and we'll change it, but we wanted to make these fixes available in a build for users who are having problems. We're not trying to represent it as anything other then a distribution that incorporates fixes users need. The build is available here: http://people.apache.org/~jvanzyl Summary of the issues Fixes pushed back to the ASF: [MNG-5064][1] mvn -nsu (--no-snapshot-updates) should not download snapshots (and break local builds) [MNG-5131][2] Wrong encoding for encrypted passwords [MNG-5113][3] NullPointerException on javadoc site generation [MNG-5137][4] Reactor resolution does not work for forked multi module builds [MNG-5096][5]exclusion ondependency with typetest-jar/type doesn't work in maven 3 [MNG-5135][6] Regression: in some cases aggregator mojo is unable to resolve dependencies with custom packaging Fixes not pushed back to the ASF as these are dependent on fixes in Eclipse Aether and Eclipse Sisu: [MNG-5042][7] Regression: CloningClassLoader causes StackOverflowError in groovy [MNG-5056][8] Test dependencies get packaged into WAR file. [MNG-5084][9] Resolver for plugins failing [MNG-5087][10] Maven 3 dependency resolution fails until maven-metadata-local.xml files (created by maven-invoker-plugin) are deleted [MNG-5125] [11]Regression: mvn 3.0.3 is extreemly slow with a large number of dependencies [MNG-5138][12] Dependency conflicts are extremely opaque [1]: http://jira.codehaus.org/browse/MNG-5064 [2]: http://jira.codehaus.org/browse/MNG-5131 [3]: http://jira.codehaus.org/browse/MNG-5113 [4]: http://jira.codehaus.org/browse/MNG-5137 [5]: http://jira.codehaus.org/browse/MNG-5096 [6]: http://jira.codehaus.org/browse/MNG-5135 [7]: http://jira.codehaus.org/browse/MNG-5042 [8]: http://jira.codehaus.org/browse/MNG-5056 [9]: http://jira.codehaus.org/browse/MNG-5084 [10]: http://jira.codehaus.org/browse/MNG-5087 [11]: http://jira.codehaus.org/browse/MNG-5125 [12]: http://jira.codehaus.org/browse/MNG-5138 [a]: http://eclipse.org/proposals/technology.aether/ [b]: http://eclipse.org/proposals/technology.sisu/ Thanks, Jason -- Jason van Zyl Eclipse Board Member Founder, Apache Maven http://twitter.com/jvanzyl - If I find ten thousand ways something won't work, I haven't failed. I am not discouraged, because every wrong attempt discarded is just one more step forward. -- Thomas Edison Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl - Our achievements speak for themselves. What we have to keep track of are our failures, discouragements and doubts. We tend to forget the past difficulties, the many false starts, and the painful groping. We see our past achievements as the end result of a clean forward thrust, and our present difficulties as signs of decline and decay. -- Eric Hoffer, Reflections on the Human Condition Thanks, Jason --
Re: Apache Maven distribution with fixes
On Jul 28, 2011, at 10:23 AM, Mark Struberg wrote: The reason why no one committed to Aether beside yourself is partly that it requires to sign some CLA which only unilaterally grants rights (as we can certainly see now!). Have you read the Sonatype CLA? The contributor keeps retains copyright and Sonatype is granted the license. Much the same way the Apache or Eclipse CLAs work. We changed that a long time ago when Brett pointed it out. Additionally Hervé and Kristian signed the CLA. It's not just Sonatype employees. Which is another reason why I consider a fork to apache-extras a good idea. And don't come me with the argument that the Maven community is not able to maintain Maven without your help. At least there IS now a CI environment. And remember who built the git stuff on which your whole company is based upon? I'm not sure what you're referring to, we don't even sell anything with git in it. m2eclipse has an m2eclipse-egit connector but we stopped using jgit-simple, if that's the work you're referring to, and use the JGit APIs directly now[1]. The argument is not that we cannot fix it becaues we are dumb little bunnies, but because the code is not under our control anymore! I specifically said that folks here, from empirical observation, do not have the time or energy. Additionally I would say you don't have much experience in the Aether and Sisu codebases. I most definitely did not say you were dumb, or didn't have the aptitude. But having the aptitude still puts you a long way from working with the code effectively. There's nothing magical about it, it's the same as any other body of code in that it takes time, and energy to learn and gain experience with a new codebase and become effective with it. [1]: https://github.com/sonatype/m2eclipse-egit/blob/master/org.sonatype.m2e.egit.target-platform/e37.target LieGrue, strub --- On Thu, 7/28/11, Jason van Zyl ja...@sonatype.com wrote: From: Jason van Zyl ja...@sonatype.com Subject: Re: Apache Maven distribution with fixes To: Maven Developers List dev@maven.apache.org Date: Thursday, July 28, 2011, 1:23 PM On Jul 28, 2011, at 8:52 AM, Mark Struberg wrote: Humm, guess there are only 3 options left in this case 1.) We wait 7 weeks or whatever time it takes (most probably it _will_ take more) Not likely, it will probably be shorter as I was being conservative. The scheduling at Eclipse is like a clockwork. Once the review period of over the creation review is immediately scheduled. The creation review and initial legal review will have no issues because nearly 100% of the code was written by Sonatype employees and we're all cleared at Eclipse. The code will start the parallel IP immediately and probably clear IP review very fast given it's all Sonatype code and there is already precedent for a lot of our code going into Eclipse. 2.) You ship an ALv2 licensed version of Aether and Sisu which we can incorporate into an upcoming maven-3.0.4. The proposals are posted, I'm not changing the licenses now. 3.) We fork the last ALv2 licensed Aether version back to the Maven project and fix the bugs ourself. I believe this will never happen and you will put the project in a very bad place if you attempt to do that. Since our last release not a single Maven committer outside of Sonatype has made any bug fixes or patches to the core (Paul made one small feature addition). You guys are talking about a new wagon, POM5 formats, new logging, artifact lookup indirection, but the day to day of actually patching and bug fixing is entirely absent and things like the plugin ITs are failing day after day in CI. Looking at the situation empirically, the probability that you will have the time and energy to try and patch Aether and Sisu given no one has patched any of the normal core code here I find a highly impractical and dangerous proposal. Path 1) doesn't preclude your participation and we've done nothing to hinder Kristian or Herve from participating. LieGrue, strub --- On Thu, 7/28/11, Jason van Zyl ja...@sonatype.com wrote: From: Jason van Zyl ja...@sonatype.com Subject: Re: Apache Maven distribution with fixes To: Maven Developers List dev@maven.apache.org Date: Thursday, July 28, 2011, 12:32 PM On Jul 28, 2011, at 8:25 AM, Mark Struberg wrote: mom jason. Before we ship 3.0.4 I'd like to fix the SCM URL postfix problem which exists in lots of DSCMs. Will do this in the next week. You probably have 6-7 weeks before an official 3.0.4 release would be made so you have plenty of time. If you are going to wait for Aether and Sisu to be provisioned at Eclipse then the total time for both of those to pass into that state is about 7 weeks. The build I proposed could not be an official release until such a time because there are fixes which rely on Sisu and Aether which are important for users. LieGrue, strub
Re: Apache Maven distribution with fixes
On 7/28/11 10:43 AM, Jason van Zyl wrote: On Jul 28, 2011, at 10:23 AM, Mark Struberg wrote: The reason why no one committed to Aether beside yourself is partly that it requires to sign some CLA which only unilaterally grants rights (as we can certainly see now!). Have you read the Sonatype CLA? The contributor keeps retains copyright and Sonatype is granted the license. Much the same way the Apache or Eclipse CLAs work. We changed that a long time ago when Brett pointed it out. Additionally Hervé and Kristian signed the CLA. It's not just Sonatype employees. So you had to get approval from all contributors before switching to EPl-only? Which is another reason why I consider a fork to apache-extras a good idea. And don't come me with the argument that the Maven community is not able to maintain Maven without your help. At least there IS now a CI environment. And remember who built the git stuff on which your whole company is based upon? I'm not sure what you're referring to, we don't even sell anything with git in it. m2eclipse has an m2eclipse-egit connector but we stopped using jgit-simple, if that's the work you're referring to, and use the JGit APIs directly now[1]. The argument is not that we cannot fix it becaues we are dumb little bunnies, but because the code is not under our control anymore! I specifically said that folks here, from empirical observation, do not have the time or energy. Additionally I would say you don't have much experience in the Aether and Sisu codebases. I most definitely did not say you were dumb, or didn't have the aptitude. But having the aptitude still puts you a long way from working with the code effectively. There's nothing magical about it, it's the same as any other body of code in that it takes time, and energy to learn and gain experience with a new codebase and become effective with it. [1]: https://github.com/sonatype/m2eclipse-egit/blob/master/org.sonatype.m2e.egit.target-platform/e37.target LieGrue, strub --- On Thu, 7/28/11, Jason van Zylja...@sonatype.com wrote: From: Jason van Zylja...@sonatype.com Subject: Re: Apache Maven distribution with fixes To: Maven Developers Listdev@maven.apache.org Date: Thursday, July 28, 2011, 1:23 PM On Jul 28, 2011, at 8:52 AM, Mark Struberg wrote: Humm, guess there are only 3 options left in this case 1.) We wait 7 weeks or whatever time it takes (most probably it _will_ take more) Not likely, it will probably be shorter as I was being conservative. The scheduling at Eclipse is like a clockwork. Once the review period of over the creation review is immediately scheduled. The creation review and initial legal review will have no issues because nearly 100% of the code was written by Sonatype employees and we're all cleared at Eclipse. The code will start the parallel IP immediately and probably clear IP review very fast given it's all Sonatype code and there is already precedent for a lot of our code going into Eclipse. 2.) You ship an ALv2 licensed version of Aether and Sisu which we can incorporate into an upcoming maven-3.0.4. The proposals are posted, I'm not changing the licenses now. 3.) We fork the last ALv2 licensed Aether version back to the Maven project and fix the bugs ourself. I believe this will never happen and you will put the project in a very bad place if you attempt to do that. Since our last release not a single Maven committer outside of Sonatype has made any bug fixes or patches to the core (Paul made one small feature addition). You guys are talking about a new wagon, POM5 formats, new logging, artifact lookup indirection, but the day to day of actually patching and bug fixing is entirely absent and things like the plugin ITs are failing day after day in CI. Looking at the situation empirically, the probability that you will have the time and energy to try and patch Aether and Sisu given no one has patched any of the normal core code here I find a highly impractical and dangerous proposal. Path 1) doesn't preclude your participation and we've done nothing to hinder Kristian or Herve from participating. LieGrue, strub --- On Thu, 7/28/11, Jason van Zylja...@sonatype.com wrote: From: Jason van Zylja...@sonatype.com Subject: Re: Apache Maven distribution with fixes To: Maven Developers Listdev@maven.apache.org Date: Thursday, July 28, 2011, 12:32 PM On Jul 28, 2011, at 8:25 AM, Mark Struberg wrote: mom jason. Before we ship 3.0.4 I'd like to fix the SCM URL postfix problem which exists in lots of DSCMs. Will do this in the next week. You probably have 6-7 weeks before an official 3.0.4 release would be made so you have plenty of time. If you are going to wait for Aether and Sisu to be provisioned at Eclipse then the total time for both of those to pass into that state is about 7 weeks. The build I proposed could not be an official release until such a time because there are fixes which rely on Sisu
Re: Apache Maven distribution with fixes
On 28 July 2011 16:03, John Casey jdca...@commonjava.org wrote: On 7/28/11 10:43 AM, Jason van Zyl wrote: On Jul 28, 2011, at 10:23 AM, Mark Struberg wrote: The reason why no one committed to Aether beside yourself is partly that it requires to sign some CLA which only unilaterally grants rights (as we can certainly see now!). Have you read the Sonatype CLA? The contributor keeps retains copyright [OT] I've just read it now... it seems entirely one-sided it is all Contributor grants rights to Sonatype, but it seems to me that there is nothing return... IANAL, but AFAIK such one-sided contracts can become null and void... certainly I have been advised that in Ireland a 1-sided contract cannot be made to stand up in court... I do hope for Sonatype's sake that you have the contract rooted in a jurisdiction that permits 1-sided contracts. [/OT] and Sonatype is granted the license. Much the same way the Apache or Eclipse CLAs work. We changed that a long time ago when Brett pointed it out. Additionally Hervé and Kristian signed the CLA. It's not just Sonatype employees. So you had to get approval from all contributors before switching to EPl-only? I'm curious to hear your answer to this - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Apache Maven distribution with fixes
On Thu, Jul 28, 2011 at 5:11 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: On 28 July 2011 16:03, John Casey jdca...@commonjava.org wrote: On 7/28/11 10:43 AM, Jason van Zyl wrote: On Jul 28, 2011, at 10:23 AM, Mark Struberg wrote: The reason why no one committed to Aether beside yourself is partly that it requires to sign some CLA which only unilaterally grants rights (as we can certainly see now!). Have you read the Sonatype CLA? The contributor keeps retains copyright [OT] I've just read it now... it seems entirely one-sided it is all Contributor grants rights to Sonatype, but it seems to me that there is nothing return... IANAL, but AFAIK such one-sided contracts can become null and void... certainly I have been advised that in Ireland a 1-sided contract cannot be made to stand up in court... I do hope for Sonatype's sake that you have the contract rooted in a jurisdiction that permits 1-sided contracts. [/OT] it seems unlikely. The same sort of agreement is signed by everyone contributing to netbeans and sun changed the license once or twice as well. same with eclipse I think. and Sonatype is granted the license. Much the same way the Apache or Eclipse CLAs work. We changed that a long time ago when Brett pointed it out. Additionally Hervé and Kristian signed the CLA. It's not just Sonatype employees. So you had to get approval from all contributors before switching to EPl-only? the point if CLA is not to have to hunt to all past contributors when changing license AFAIK. Milos I'm curious to hear your answer to this - 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: Apache Maven distribution with fixes
Not sure what version you're reading but we specifically changed so that said author retains copyright and Sonatype is granted a perpetual license. Changed specifically when Brett brought it up, we brought it in line with what Apache and Eclipse do. On Jul 28, 2011, at 11:11 AM, Stephen Connolly wrote: On 28 July 2011 16:03, John Casey jdca...@commonjava.org wrote: On 7/28/11 10:43 AM, Jason van Zyl wrote: On Jul 28, 2011, at 10:23 AM, Mark Struberg wrote: The reason why no one committed to Aether beside yourself is partly that it requires to sign some CLA which only unilaterally grants rights (as we can certainly see now!). Have you read the Sonatype CLA? The contributor keeps retains copyright [OT] I've just read it now... it seems entirely one-sided it is all Contributor grants rights to Sonatype, but it seems to me that there is nothing return... IANAL, but AFAIK such one-sided contracts can become null and void... certainly I have been advised that in Ireland a 1-sided contract cannot be made to stand up in court... I do hope for Sonatype's sake that you have the contract rooted in a jurisdiction that permits 1-sided contracts. [/OT] and Sonatype is granted the license. Much the same way the Apache or Eclipse CLAs work. We changed that a long time ago when Brett pointed it out. Additionally Hervé and Kristian signed the CLA. It's not just Sonatype employees. So you had to get approval from all contributors before switching to EPl-only? I'm curious to hear your answer to this - 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, Apache Maven http://twitter.com/jvanzyl -
Re: Apache Maven distribution with fixes
On Jul 28, 2011, at 11:03 AM, John Casey wrote: On 7/28/11 10:43 AM, Jason van Zyl wrote: On Jul 28, 2011, at 10:23 AM, Mark Struberg wrote: The reason why no one committed to Aether beside yourself is partly that it requires to sign some CLA which only unilaterally grants rights (as we can certainly see now!). Have you read the Sonatype CLA? The contributor keeps retains copyright and Sonatype is granted the license. Much the same way the Apache or Eclipse CLAs work. We changed that a long time ago when Brett pointed it out. Additionally Hervé and Kristian signed the CLA. It's not just Sonatype employees. So you had to get approval from all contributors before switching to EPl-only? Sonatype is granted perpetual rights which includes relicensing. But Hervé and Kristian are free do to whatever with their contributions i.e. push them into a fork of Aether or Sisu. I believe that we changed the contributor gets perpetual rights to Sonatype gets perpetual rights after most/all of their contributions but if they wanted to take their code and do whatever with it we'd grant it back regardless of the date of the license change. Thanks, Jason -- Jason van Zyl 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: Apache Maven distribution with fixes
On 28 July 2011 16:18, Milos Kleint mkle...@gmail.com wrote: On Thu, Jul 28, 2011 at 5:11 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: On 28 July 2011 16:03, John Casey jdca...@commonjava.org wrote: On 7/28/11 10:43 AM, Jason van Zyl wrote: On Jul 28, 2011, at 10:23 AM, Mark Struberg wrote: The reason why no one committed to Aether beside yourself is partly that it requires to sign some CLA which only unilaterally grants rights (as we can certainly see now!). Have you read the Sonatype CLA? The contributor keeps retains copyright [OT] I've just read it now... it seems entirely one-sided it is all Contributor grants rights to Sonatype, but it seems to me that there is nothing return... IANAL, but AFAIK such one-sided contracts can become null and void... certainly I have been advised that in Ireland a 1-sided contract cannot be made to stand up in court... I do hope for Sonatype's sake that you have the contract rooted in a jurisdiction that permits 1-sided contracts. [/OT] it seems unlikely. The same sort of agreement is signed by everyone contributing to netbeans and sun changed the license once or twice as well. same with eclipse I think. The eclipse one grants the contributor write access in return for certain grants of rights to eclipse. same for sun and netbeans, but the sonatype cla that I found via google: http://www.sonatype.org/SonatypeCLA.pdf does not give commit access and specifically states that sonatype may never use the submitted patches... that is why I think it is one-sided... and that is where I have the question. If I am looking at the wrong CLA, fair enough and Sonatype is granted the license. Much the same way the Apache or Eclipse CLAs work. We changed that a long time ago when Brett pointed it out. Additionally Hervé and Kristian signed the CLA. It's not just Sonatype employees. So you had to get approval from all contributors before switching to EPl-only? the point if CLA is not to have to hunt to all past contributors when changing license AFAIK. Milos I'm curious to hear your answer to this - 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
