Re: [DISCUSS] release maven-3.0.4 now with the old aether
Please - for the love of ANY Maven user - please do NOT roll a 3.0.4 with any Aether thats NOT 1.12. 1.11 that ships with the current Maven 3.0.3 has fundamental issues with your local repository has artifacts from both mirrors and non-mirrors. I'm finding more and more users getting hit with this problem that getting a release out there that doesn't solve this will just garner a -1 vote from me. Note that this problem exists also in Maven 2.x so has been around before Aether itself existed. If we're planning to roll a release with the Eclipse based Aether release, then please roll with 1.12 which fixes known issues, with the intention to roll the final release with a new, Eclipse based Aether release. On 19/08/2011, at 9:34 PM, Mark Struberg wrote: Should we create a 3.0.4 with the old aether package names now and start with the upgrade later?
Re: [DISCUSS] release maven-3.0.4 now with the old aether
Sorry Mark, exactly this solution has explicitly been vetoed with the vast majority of -1 because of various other reasons. If we release 3.0.4 now, a user might still update his local maven installation to 1.12 easily. So I see no downside to the current status quo. LieGrue, strub --- On Sat, 8/20/11, Mark Derricutt m...@talios.com wrote: From: Mark Derricutt m...@talios.com Subject: Re: [DISCUSS] release maven-3.0.4 now with the old aether To: Maven Developers List dev@maven.apache.org Date: Saturday, August 20, 2011, 10:46 AM Please - for the love of ANY Maven user - please do NOT roll a 3.0.4 with any Aether thats NOT 1.12. 1.11 that ships with the current Maven 3.0.3 has fundamental issues with your local repository has artifacts from both mirrors and non-mirrors. I'm finding more and more users getting hit with this problem that getting a release out there that doesn't solve this will just garner a -1 vote from me. Note that this problem exists also in Maven 2.x so has been around before Aether itself existed. If we're planning to roll a release with the Eclipse based Aether release, then please roll with 1.12 which fixes known issues, with the intention to roll the final release with a new, Eclipse based Aether release. On 19/08/2011, at 9:34 PM, Mark Struberg wrote: Should we create a 3.0.4 with the old aether package names now and start with the upgrade later? - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [DISCUSS] release maven-3.0.4 now with the old aether
Only that the majority of users will get just get unable to resolve artifact errors, and probably never know that they can update aether - which, whilst it isn't a difficult thing to do is just a bit fiddly - instead they'll just get frustrated that once again maven black magic sucks. If rolling without 1.12 of aether, could we at least mention clearly in whatever release notes are blogged/emailed out that if they encounter such issues, they can be resolved with an Aether update. Still, I guess things could be worse - we could be using a build tool built on Ivy. On 20/08/2011, at 10:59 PM, Mark Struberg wrote: If we release 3.0.4 now, a user might still update his local maven installation to 1.12 easily. So I see no downside to the current status quo.
Re: [DISCUSS] release maven-3.0.4 now with the old aether
3/4 weeks ago we should/may have done a release of 3.0.4 with existing Aether/Sisu dependencies (thus yes existing ones are from Sonatype but are dual licensed ASL/EPL - or maybe full ASL I don't remember). Arnaud On Fri, Aug 19, 2011 at 4:07 PM, Anders Hammar and...@hammar.net wrote: Arnaud, are you talking about a Maven 3.0.4 release with Eclipse Aether+Sisu or with Sonatype Aether+Sisu? /Anders 2011/8/19 Arnaud Héritier aherit...@gmail.com: I'm thinking like Jason. If we wanted we to release 3.0.4 without Aether we should have done that 2 or 3 weeks ago (I think Wagon 1.0 was already ready ?). I'm almost sure that Jason will convince Eclipse to keep the current identity of these projects (at least for a period of time to let him schedule a migration perhaps for a next major release of them). Thus we might able to work on a 3.0.4 release with everything at the end of next week. I would like also to release early/often and I really dislike that our team never succeeded to do it (it goes with various wrong project management part like having a Roadmap and things like that). But in that case I think we should wait for 1 week as I know us and the next one will never be done one week later On Fri, Aug 19, 2011 at 3:05 PM, Jason van Zyl ja...@maven.org wrote: As long as we reach consensus about whether we should release. At this point we've wait this long, if we were going to release 3.0.4 sans Aether 1.12 we should have done it a month ago. Right now the best thing for users is to make the best possible release and that includes Aether 1.12 which poses no risk to anyone at this point. On Aug 19, 2011, at 8:41 AM, Mark Struberg wrote: There is more beyond that. Remember that we also upgraded to wagon-1.0 which had some _serious_ fixes, etc. + upgrade to the new apache parent and other stuff which have been no maven-core part directly, but got fixed subsequently. LieGrue, strub --- On Fri, 8/19/11, Jason van Zyl ja...@maven.org wrote: From: Jason van Zyl ja...@maven.org Subject: Re: [DISCUSS] release maven-3.0.4 now with the old aether To: Maven Developers List dev@maven.apache.org Date: Friday, August 19, 2011, 11:45 AM I think we should wait for the vote to finish as it appears the vote will pass and then a release can be made that users actually want. That fixes are are most requested fall into the category of requiring the newer versions of Aether and Sisu. I'm certain users would be more interested in having a version with Aether 1.12 which has been released. So if we don't want to cut a release with that in it then waiting another month, I believe, is better than rushing out some release now with 6 fixes which are minor and making all users drop in libraries themselves to fix the issues that are hurting them most. If we want to wait for official Eclipse releases then we should just wait. Users who are on the dev list feel free to chime in. Summary of the issues [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 On Aug 19, 2011, at 7:32 AM, Mark Struberg wrote: I think the outcome of the other vote doesn't change much. The following scenarios are possible: a.) The vote fails and maven stays at aether 1.11. In this case we still should ship a 3.0.4 to fix a few bugs on our side. b.) The vote passes and aether @eclipse must change package names + GAV then it will certainly take a bit time on both sides. So users still could upgrade to aether-1.12 manually if they want. c.) The vote passes and aether GAV and package names are allowed to remain com.sonatype.* In this case users might also manually update if they want. In any case we should
Re: [DISCUSS] release maven-3.0.4 now with the old aether
+1 from me too. Kristian Den 19.08.2011 11:34, skrev Mark Struberg: Hi folks! I know aether @eclipse should be starting in the next weeks. But it will certainly take a few more weeks to get all the packages renamed (most probably), etc. Should we create a 3.0.4 with the old aether package names now and start with the upgrade later? +1 from me. LieGrue, strub - 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: [DISCUSS] release maven-3.0.4 now with the old aether
Den 19.08.2011 11:34, skrev Mark Struberg: Hi folks! I know aether @eclipse should be starting in the next weeks. But it will certainly take a few more weeks to get all the packages renamed (most probably), etc. Should we create a 3.0.4 with the old aether package names now and start with the upgrade later? +1 from me. LieGrue, strub - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org If we could plan it for early next week I'll see if I can get some MNG issues done over the weekend. Kristian - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [DISCUSS] release maven-3.0.4 now with the old aether
Mark, I think you're jumping the gun a bit. The vote that Arnaud proposed is not finished yet. Many PMC members have not voted yet and at the very least to short-circuit the vote we need to reach a majority amongst the PMC. Once that happens then I think we can start discussing a 3.0.4 release. On Aug 19, 2011, at 5:34 AM, Mark Struberg wrote: Hi folks! I know aether @eclipse should be starting in the next weeks. But it will certainly take a few more weeks to get all the packages renamed (most probably), etc. Should we create a 3.0.4 with the old aether package names now and start with the upgrade later? +1 from me. LieGrue, strub - 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 - Simplex sigillum veri. (Simplicity is the seal of truth.)
Re: [DISCUSS] release maven-3.0.4 now with the old aether
I think the outcome of the other vote doesn't change much. The following scenarios are possible: a.) The vote fails and maven stays at aether 1.11. In this case we still should ship a 3.0.4 to fix a few bugs on our side. b.) The vote passes and aether @eclipse must change package names + GAV then it will certainly take a bit time on both sides. So users still could upgrade to aether-1.12 manually if they want. c.) The vote passes and aether GAV and package names are allowed to remain com.sonatype.* In this case users might also manually update if they want. In any case we should ship maven-3.0.5 once there is a new aether version shipped by the Eclipse Foundation AND we did run sufficient tests with this version on our side. LieGrue, strub --- On Fri, 8/19/11, Jason van Zyl ja...@maven.org wrote: From: Jason van Zyl ja...@maven.org Subject: Re: [DISCUSS] release maven-3.0.4 now with the old aether To: Maven Developers List dev@maven.apache.org Date: Friday, August 19, 2011, 11:09 AM Mark, I think you're jumping the gun a bit. The vote that Arnaud proposed is not finished yet. Many PMC members have not voted yet and at the very least to short-circuit the vote we need to reach a majority amongst the PMC. Once that happens then I think we can start discussing a 3.0.4 release. On Aug 19, 2011, at 5:34 AM, Mark Struberg wrote: Hi folks! I know aether @eclipse should be starting in the next weeks. But it will certainly take a few more weeks to get all the packages renamed (most probably), etc. Should we create a 3.0.4 with the old aether package names now and start with the upgrade later? +1 from me. LieGrue, strub - 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 - Simplex sigillum veri. (Simplicity is the seal of truth.) - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [DISCUSS] release maven-3.0.4 now with the old aether
I misread you, sloppy of me. EPL aether waits; we could do 3.0.4 for other non-aether stuff. Kristian Den 19.08.2011 13:32, skrev Mark Struberg: I think the outcome of the other vote doesn't change much. The following scenarios are possible: a.) The vote fails and maven stays at aether 1.11. In this case we still should ship a 3.0.4 to fix a few bugs on our side. b.) The vote passes and aether @eclipse must change package names + GAV then it will certainly take a bit time on both sides. So users still could upgrade to aether-1.12 manually if they want. c.) The vote passes and aether GAV and package names are allowed to remain com.sonatype.* In this case users might also manually update if they want. In any case we should ship maven-3.0.5 once there is a new aether version shipped by the Eclipse Foundation AND we did run sufficient tests with this version on our side. LieGrue, strub --- On Fri, 8/19/11, Jason van Zylja...@maven.org wrote: From: Jason van Zylja...@maven.org Subject: Re: [DISCUSS] release maven-3.0.4 now with the old aether To: Maven Developers Listdev@maven.apache.org Date: Friday, August 19, 2011, 11:09 AM Mark, I think you're jumping the gun a bit. The vote that Arnaud proposed is not finished yet. Many PMC members have not voted yet and at the very least to short-circuit the vote we need to reach a majority amongst the PMC. Once that happens then I think we can start discussing a 3.0.4 release. On Aug 19, 2011, at 5:34 AM, Mark Struberg wrote: Hi folks! I know aether @eclipse should be starting in the next weeks. But it will certainly take a few more weeks to get all the packages renamed (most probably), etc. Should we create a 3.0.4 with the old aether package names now and start with the upgrade later? +1 from me. LieGrue, strub - 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 - Simplex sigillum veri. (Simplicity is the seal of truth.) - 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: [DISCUSS] release maven-3.0.4 now with the old aether
+1. It seems a sensible plan to me. First release a 3.0.4 ASAP to show Maven keeps moving. Then release a 3.0.5 when Aether and Sisu will have thoroughly finished their landings at eclipse. Cheers Le 19 août 2011 13:32, Mark Struberg strub...@yahoo.de a écrit : I think the outcome of the other vote doesn't change much. The following scenarios are possible: a.) The vote fails and maven stays at aether 1.11. In this case we still should ship a 3.0.4 to fix a few bugs on our side. b.) The vote passes and aether @eclipse must change package names + GAV then it will certainly take a bit time on both sides. So users still could upgrade to aether-1.12 manually if they want. c.) The vote passes and aether GAV and package names are allowed to remain com.sonatype.* In this case users might also manually update if they want. In any case we should ship maven-3.0.5 once there is a new aether version shipped by the Eclipse Foundation AND we did run sufficient tests with this version on our side. LieGrue, strub --- On Fri, 8/19/11, Jason van Zyl ja...@maven.org wrote: From: Jason van Zyl ja...@maven.org Subject: Re: [DISCUSS] release maven-3.0.4 now with the old aether To: Maven Developers List dev@maven.apache.org Date: Friday, August 19, 2011, 11:09 AM Mark, I think you're jumping the gun a bit. The vote that Arnaud proposed is not finished yet. Many PMC members have not voted yet and at the very least to short-circuit the vote we need to reach a majority amongst the PMC. Once that happens then I think we can start discussing a 3.0.4 release. On Aug 19, 2011, at 5:34 AM, Mark Struberg wrote: Hi folks! I know aether @eclipse should be starting in the next weeks. But it will certainly take a few more weeks to get all the packages renamed (most probably), etc. Should we create a 3.0.4 with the old aether package names now and start with the upgrade later? +1 from me. LieGrue, strub - 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 - Simplex sigillum veri. (Simplicity is the seal of truth.) - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [DISCUSS] release maven-3.0.4 now with the old aether
I think we should wait for the vote to finish as it appears the vote will pass and then a release can be made that users actually want. That fixes are are most requested fall into the category of requiring the newer versions of Aether and Sisu. I'm certain users would be more interested in having a version with Aether 1.12 which has been released. So if we don't want to cut a release with that in it then waiting another month, I believe, is better than rushing out some release now with 6 fixes which are minor and making all users drop in libraries themselves to fix the issues that are hurting them most. If we want to wait for official Eclipse releases then we should just wait. Users who are on the dev list feel free to chime in. Summary of the issues [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 On Aug 19, 2011, at 7:32 AM, Mark Struberg wrote: I think the outcome of the other vote doesn't change much. The following scenarios are possible: a.) The vote fails and maven stays at aether 1.11. In this case we still should ship a 3.0.4 to fix a few bugs on our side. b.) The vote passes and aether @eclipse must change package names + GAV then it will certainly take a bit time on both sides. So users still could upgrade to aether-1.12 manually if they want. c.) The vote passes and aether GAV and package names are allowed to remain com.sonatype.* In this case users might also manually update if they want. In any case we should ship maven-3.0.5 once there is a new aether version shipped by the Eclipse Foundation AND we did run sufficient tests with this version on our side. LieGrue, strub --- On Fri, 8/19/11, Jason van Zyl ja...@maven.org wrote: From: Jason van Zyl ja...@maven.org Subject: Re: [DISCUSS] release maven-3.0.4 now with the old aether To: Maven Developers List dev@maven.apache.org Date: Friday, August 19, 2011, 11:09 AM Mark, I think you're jumping the gun a bit. The vote that Arnaud proposed is not finished yet. Many PMC members have not voted yet and at the very least to short-circuit the vote we need to reach a majority amongst the PMC. Once that happens then I think we can start discussing a 3.0.4 release. On Aug 19, 2011, at 5:34 AM, Mark Struberg wrote: Hi folks! I know aether @eclipse should be starting in the next weeks. But it will certainly take a few more weeks to get all the packages renamed (most probably), etc. Should we create a 3.0.4 with the old aether package names now and start with the upgrade later? +1 from me. LieGrue, strub - 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 - Simplex sigillum veri. (Simplicity is the seal of truth.) - 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 - There's no sense in being precise when you don't even know what you're talking about. -- John von Neumann
Re: [DISCUSS] release maven-3.0.4 now with the old aether
There is more beyond that. Remember that we also upgraded to wagon-1.0 which had some _serious_ fixes, etc. + upgrade to the new apache parent and other stuff which have been no maven-core part directly, but got fixed subsequently. LieGrue, strub --- On Fri, 8/19/11, Jason van Zyl ja...@maven.org wrote: From: Jason van Zyl ja...@maven.org Subject: Re: [DISCUSS] release maven-3.0.4 now with the old aether To: Maven Developers List dev@maven.apache.org Date: Friday, August 19, 2011, 11:45 AM I think we should wait for the vote to finish as it appears the vote will pass and then a release can be made that users actually want. That fixes are are most requested fall into the category of requiring the newer versions of Aether and Sisu. I'm certain users would be more interested in having a version with Aether 1.12 which has been released. So if we don't want to cut a release with that in it then waiting another month, I believe, is better than rushing out some release now with 6 fixes which are minor and making all users drop in libraries themselves to fix the issues that are hurting them most. If we want to wait for official Eclipse releases then we should just wait. Users who are on the dev list feel free to chime in. Summary of the issues [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 On Aug 19, 2011, at 7:32 AM, Mark Struberg wrote: I think the outcome of the other vote doesn't change much. The following scenarios are possible: a.) The vote fails and maven stays at aether 1.11. In this case we still should ship a 3.0.4 to fix a few bugs on our side. b.) The vote passes and aether @eclipse must change package names + GAV then it will certainly take a bit time on both sides. So users still could upgrade to aether-1.12 manually if they want. c.) The vote passes and aether GAV and package names are allowed to remain com.sonatype.* In this case users might also manually update if they want. In any case we should ship maven-3.0.5 once there is a new aether version shipped by the Eclipse Foundation AND we did run sufficient tests with this version on our side. LieGrue, strub --- On Fri, 8/19/11, Jason van Zyl ja...@maven.org wrote: From: Jason van Zyl ja...@maven.org Subject: Re: [DISCUSS] release maven-3.0.4 now with the old aether To: Maven Developers List dev@maven.apache.org Date: Friday, August 19, 2011, 11:09 AM Mark, I think you're jumping the gun a bit. The vote that Arnaud proposed is not finished yet. Many PMC members have not voted yet and at the very least to short-circuit the vote we need to reach a majority amongst the PMC. Once that happens then I think we can start discussing a 3.0.4 release. On Aug 19, 2011, at 5:34 AM, Mark Struberg wrote: Hi folks! I know aether @eclipse should be starting in the next weeks. But it will certainly take a few more weeks to get all the packages renamed (most probably), etc. Should we create a 3.0.4 with the old aether package names now and start with the upgrade later? +1 from me. LieGrue, strub - 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 - Simplex sigillum veri. (Simplicity is the seal of truth.) - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org Thanks, Jason
Re: [DISCUSS] release maven-3.0.4 now with the old aether
I'll add my opinion as a Maven user and someone outside of the dev team: My first hand choice would be a 3.0.4 with Aether and Sisu fixes. My take on the discussions is that including Aether 1.12 is possible license vice, but there was some concerns having a dependency on something not being within the control of the devs. But if it was at Eclipse everyone (or at least a majority) was fine with it. So, if the ongoing vote passes, wouldn't it be ok to release 3.0.4 with the latest existing Aether and Sisu releases from Sonatype (here I assume that what's being moved to Eclipse is that exact code). Any fixes for that code would then be handled over at Eclipse and used in future Maven releases. After that, the work could start to adapt Maven in what ever way to use the upcoming releases from the new Eclipse projects. It should give you time to do this without rushing and at the same time keep us users happy. :-) I'm also thinking that the release process (vote) on 3.0.4 could start in parallel with the ongoing Aether/Sisu Eclipse/EPL vote and have a dependency to that outcome. Would that be possible? If so, 3.0.4 (if the vote passes) could be released right after Aether and Sisu is accepted at Eclipse (next week I take it if everything goes according to plan). If the above isn't feasible, I would rather see 3.0.4 without Aether/Sisu fixes released soon than 3.0.4 with Aether/Sisu fixes released in a month. In my opinion it's more important to get a new version out than trying to get as many bug fixes as possible fixed. I know this might not make sense from a usage perspective, but I'm more worried about what people thinks just looking at how long it takes between releases. Release early, release often. /Anders On Fri, Aug 19, 2011 at 13:45, Jason van Zyl ja...@maven.org wrote: I think we should wait for the vote to finish as it appears the vote will pass and then a release can be made that users actually want. That fixes are are most requested fall into the category of requiring the newer versions of Aether and Sisu. I'm certain users would be more interested in having a version with Aether 1.12 which has been released. So if we don't want to cut a release with that in it then waiting another month, I believe, is better than rushing out some release now with 6 fixes which are minor and making all users drop in libraries themselves to fix the issues that are hurting them most. If we want to wait for official Eclipse releases then we should just wait. Users who are on the dev list feel free to chime in. Summary of the issues [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 On Aug 19, 2011, at 7:32 AM, Mark Struberg wrote: I think the outcome of the other vote doesn't change much. The following scenarios are possible: a.) The vote fails and maven stays at aether 1.11. In this case we still should ship a 3.0.4 to fix a few bugs on our side. b.) The vote passes and aether @eclipse must change package names + GAV then it will certainly take a bit time on both sides. So users still could upgrade to aether-1.12 manually if they want. c.) The vote passes and aether GAV and package names are allowed to remain com.sonatype.* In this case users might also manually update if they want. In any case we should ship maven-3.0.5 once there is a new aether version shipped by the Eclipse Foundation AND we did run sufficient tests with this version on our side. LieGrue, strub --- On Fri, 8/19/11, Jason van Zyl ja...@maven.org wrote: From: Jason van Zyl ja...@maven.org Subject: Re: [DISCUSS] release maven-3.0.4 now with the old aether To: Maven Developers List dev@maven.apache.org Date: Friday, August 19, 2011, 11:09 AM Mark, I think you're jumping the gun a bit. The vote that Arnaud proposed is not finished yet. Many PMC members have not voted yet and at the very least
Re: [DISCUSS] release maven-3.0.4 now with the old aether
As long as we reach consensus about whether we should release. At this point we've wait this long, if we were going to release 3.0.4 sans Aether 1.12 we should have done it a month ago. Right now the best thing for users is to make the best possible release and that includes Aether 1.12 which poses no risk to anyone at this point. On Aug 19, 2011, at 8:41 AM, Mark Struberg wrote: There is more beyond that. Remember that we also upgraded to wagon-1.0 which had some _serious_ fixes, etc. + upgrade to the new apache parent and other stuff which have been no maven-core part directly, but got fixed subsequently. LieGrue, strub --- On Fri, 8/19/11, Jason van Zyl ja...@maven.org wrote: From: Jason van Zyl ja...@maven.org Subject: Re: [DISCUSS] release maven-3.0.4 now with the old aether To: Maven Developers List dev@maven.apache.org Date: Friday, August 19, 2011, 11:45 AM I think we should wait for the vote to finish as it appears the vote will pass and then a release can be made that users actually want. That fixes are are most requested fall into the category of requiring the newer versions of Aether and Sisu. I'm certain users would be more interested in having a version with Aether 1.12 which has been released. So if we don't want to cut a release with that in it then waiting another month, I believe, is better than rushing out some release now with 6 fixes which are minor and making all users drop in libraries themselves to fix the issues that are hurting them most. If we want to wait for official Eclipse releases then we should just wait. Users who are on the dev list feel free to chime in. Summary of the issues [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 On Aug 19, 2011, at 7:32 AM, Mark Struberg wrote: I think the outcome of the other vote doesn't change much. The following scenarios are possible: a.) The vote fails and maven stays at aether 1.11. In this case we still should ship a 3.0.4 to fix a few bugs on our side. b.) The vote passes and aether @eclipse must change package names + GAV then it will certainly take a bit time on both sides. So users still could upgrade to aether-1.12 manually if they want. c.) The vote passes and aether GAV and package names are allowed to remain com.sonatype.* In this case users might also manually update if they want. In any case we should ship maven-3.0.5 once there is a new aether version shipped by the Eclipse Foundation AND we did run sufficient tests with this version on our side. LieGrue, strub --- On Fri, 8/19/11, Jason van Zyl ja...@maven.org wrote: From: Jason van Zyl ja...@maven.org Subject: Re: [DISCUSS] release maven-3.0.4 now with the old aether To: Maven Developers List dev@maven.apache.org Date: Friday, August 19, 2011, 11:09 AM Mark, I think you're jumping the gun a bit. The vote that Arnaud proposed is not finished yet. Many PMC members have not voted yet and at the very least to short-circuit the vote we need to reach a majority amongst the PMC. Once that happens then I think we can start discussing a 3.0.4 release. On Aug 19, 2011, at 5:34 AM, Mark Struberg wrote: Hi folks! I know aether @eclipse should be starting in the next weeks. But it will certainly take a few more weeks to get all the packages renamed (most probably), etc. Should we create a 3.0.4 with the old aether package names now and start with the upgrade later? +1 from me. LieGrue, strub - 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: [DISCUSS] release maven-3.0.4 now with the old aether
I'm thinking like Jason. If we wanted we to release 3.0.4 without Aether we should have done that 2 or 3 weeks ago (I think Wagon 1.0 was already ready ?). I'm almost sure that Jason will convince Eclipse to keep the current identity of these projects (at least for a period of time to let him schedule a migration perhaps for a next major release of them). Thus we might able to work on a 3.0.4 release with everything at the end of next week. I would like also to release early/often and I really dislike that our team never succeeded to do it (it goes with various wrong project management part like having a Roadmap and things like that). But in that case I think we should wait for 1 week as I know us and the next one will never be done one week later On Fri, Aug 19, 2011 at 3:05 PM, Jason van Zyl ja...@maven.org wrote: As long as we reach consensus about whether we should release. At this point we've wait this long, if we were going to release 3.0.4 sans Aether 1.12 we should have done it a month ago. Right now the best thing for users is to make the best possible release and that includes Aether 1.12 which poses no risk to anyone at this point. On Aug 19, 2011, at 8:41 AM, Mark Struberg wrote: There is more beyond that. Remember that we also upgraded to wagon-1.0 which had some _serious_ fixes, etc. + upgrade to the new apache parent and other stuff which have been no maven-core part directly, but got fixed subsequently. LieGrue, strub --- On Fri, 8/19/11, Jason van Zyl ja...@maven.org wrote: From: Jason van Zyl ja...@maven.org Subject: Re: [DISCUSS] release maven-3.0.4 now with the old aether To: Maven Developers List dev@maven.apache.org Date: Friday, August 19, 2011, 11:45 AM I think we should wait for the vote to finish as it appears the vote will pass and then a release can be made that users actually want. That fixes are are most requested fall into the category of requiring the newer versions of Aether and Sisu. I'm certain users would be more interested in having a version with Aether 1.12 which has been released. So if we don't want to cut a release with that in it then waiting another month, I believe, is better than rushing out some release now with 6 fixes which are minor and making all users drop in libraries themselves to fix the issues that are hurting them most. If we want to wait for official Eclipse releases then we should just wait. Users who are on the dev list feel free to chime in. Summary of the issues [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 On Aug 19, 2011, at 7:32 AM, Mark Struberg wrote: I think the outcome of the other vote doesn't change much. The following scenarios are possible: a.) The vote fails and maven stays at aether 1.11. In this case we still should ship a 3.0.4 to fix a few bugs on our side. b.) The vote passes and aether @eclipse must change package names + GAV then it will certainly take a bit time on both sides. So users still could upgrade to aether-1.12 manually if they want. c.) The vote passes and aether GAV and package names are allowed to remain com.sonatype.* In this case users might also manually update if they want. In any case we should ship maven-3.0.5 once there is a new aether version shipped by the Eclipse Foundation AND we did run sufficient tests with this version on our side. LieGrue, strub --- On Fri, 8/19/11, Jason van Zyl ja...@maven.org wrote: From: Jason van Zyl ja...@maven.org Subject: Re: [DISCUSS] release maven-3.0.4 now with the old aether To: Maven Developers List dev@maven.apache.org Date: Friday, August 19, 2011, 11:09 AM Mark, I think you're jumping the gun a bit. The vote that Arnaud proposed is not finished yet. Many PMC members have not voted yet
Re: [DISCUSS] release maven-3.0.4 now with the old aether
Arnaud, are you talking about a Maven 3.0.4 release with Eclipse Aether+Sisu or with Sonatype Aether+Sisu? /Anders 2011/8/19 Arnaud Héritier aherit...@gmail.com: I'm thinking like Jason. If we wanted we to release 3.0.4 without Aether we should have done that 2 or 3 weeks ago (I think Wagon 1.0 was already ready ?). I'm almost sure that Jason will convince Eclipse to keep the current identity of these projects (at least for a period of time to let him schedule a migration perhaps for a next major release of them). Thus we might able to work on a 3.0.4 release with everything at the end of next week. I would like also to release early/often and I really dislike that our team never succeeded to do it (it goes with various wrong project management part like having a Roadmap and things like that). But in that case I think we should wait for 1 week as I know us and the next one will never be done one week later On Fri, Aug 19, 2011 at 3:05 PM, Jason van Zyl ja...@maven.org wrote: As long as we reach consensus about whether we should release. At this point we've wait this long, if we were going to release 3.0.4 sans Aether 1.12 we should have done it a month ago. Right now the best thing for users is to make the best possible release and that includes Aether 1.12 which poses no risk to anyone at this point. On Aug 19, 2011, at 8:41 AM, Mark Struberg wrote: There is more beyond that. Remember that we also upgraded to wagon-1.0 which had some _serious_ fixes, etc. + upgrade to the new apache parent and other stuff which have been no maven-core part directly, but got fixed subsequently. LieGrue, strub --- On Fri, 8/19/11, Jason van Zyl ja...@maven.org wrote: From: Jason van Zyl ja...@maven.org Subject: Re: [DISCUSS] release maven-3.0.4 now with the old aether To: Maven Developers List dev@maven.apache.org Date: Friday, August 19, 2011, 11:45 AM I think we should wait for the vote to finish as it appears the vote will pass and then a release can be made that users actually want. That fixes are are most requested fall into the category of requiring the newer versions of Aether and Sisu. I'm certain users would be more interested in having a version with Aether 1.12 which has been released. So if we don't want to cut a release with that in it then waiting another month, I believe, is better than rushing out some release now with 6 fixes which are minor and making all users drop in libraries themselves to fix the issues that are hurting them most. If we want to wait for official Eclipse releases then we should just wait. Users who are on the dev list feel free to chime in. Summary of the issues [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 On Aug 19, 2011, at 7:32 AM, Mark Struberg wrote: I think the outcome of the other vote doesn't change much. The following scenarios are possible: a.) The vote fails and maven stays at aether 1.11. In this case we still should ship a 3.0.4 to fix a few bugs on our side. b.) The vote passes and aether @eclipse must change package names + GAV then it will certainly take a bit time on both sides. So users still could upgrade to aether-1.12 manually if they want. c.) The vote passes and aether GAV and package names are allowed to remain com.sonatype.* In this case users might also manually update if they want. In any case we should ship maven-3.0.5 once there is a new aether version shipped by the Eclipse Foundation AND we did run sufficient tests with this version on our side. LieGrue, strub --- On Fri, 8/19/11, Jason van Zyl ja...@maven.org wrote: From: Jason van Zyl ja...@maven.org Subject: Re: [DISCUSS] release maven-3.0.4 now with the old aether To: Maven Developers List dev@maven.apache.org Date
Re: [DISCUSS] release maven-3.0.4 now with the old aether
For what it's worth, working around Maven not having had a release since the 1.12 release of Aether has been an unwelcome hassle. (FYI, I reported one of the issues Jason mentioned, MNG-5087.) I don't have much perspective on the intricacies or history of the licensing and governance issues that have been raised re: Aether, its move to Eclipse, and so on. Suffice it to say that, as a user, it's disappointing and frustrating that that such issues appear to have stalled the release of bugfixes that presumably lots of people are waiting for and perhaps blocking on. Cheers, - Chas -- View this message in context: http://maven.40175.n5.nabble.com/DISCUSS-release-maven-3-0-4-now-with-the-old-aether-tp4715049p4716480.html Sent from the Maven Developers mailing list archive at Nabble.com. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
