Re: [ANN] First call to round up issues for 3.5.1
+1 I'll look to cutting the release at the start of September, prepare accordingly On 4 August 2017 at 05:30, Robert Scholte wrote: > On Fri, 23 Jun 2017 16:27:03 +0200, Robert Scholte > wrote: > > Looking for someone who can second the following issues: >> > Second attempt: > > >> MNG-6148: Can't package and assemble with JDK9/Jigsaw >> > > See https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit > ;h=361b902d0c01d9a2b82d4b126ecd3a228b955124 > In fact only maven-javadoc-plugin is really required, all other plugins > were already updated for other issues in 3.5.0 > > >> MNG-6127: Fix plugin execution configuration interference >> > > See https://git-wip-us.apache.org/repos/asf?p=maven-integration- > testing.git;a=commit;h=82b043f8bd2015fc4ccac35df805ec2356100428 > See https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit > ;h=57e4b331ebd41ab5337c60a7c8fc4d3d435475fb > > > >> MNG-6220: Add CLI options to control color output >> > Fixed by introducing system property style.color=[auto*|always|never] > See https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit > ;h=fd57754218e749305be1dd745fda9407960cf985 > > > >> thanks, >> Robert >> >> On Tue, 25 Apr 2017 22:43:54 +0200, Stephen Connolly < >> stephen.alan.conno...@gmail.com> wrote: >> >> I'd like people to take this next week to consider what issues we want to >>> pull in scope for 3.5.1. >>> >>> If you are a committer, just add the issues to Fix Version of >>> 3.5.1-candidate, ideally adding a comment at the same time with your >>> reasoning. >>> >>> If once we have a seconding committer, they can just comment seconding >>> and >>> move the Fix Version to 3.5.1. >>> >>> I'm going to suggest a 1 week period of open scoping. After that point in >>> time, my intent is to be more strict and apply "release manager risk >>> management" on any new issues being targeted for 3.5.1. Similarly, if >>> issues targeted for 3.5.1 are not making sufficient progress they will be >>> dropped... but for now... it's open season! >>> >>> Get triaging! >>> >>> -Stephen >>> >> >> - >> 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: [ANN] First call to round up issues for 3.5.1
On Fri, 23 Jun 2017 16:27:03 +0200, Robert Scholte wrote: Looking for someone who can second the following issues: Second attempt: MNG-6148: Can't package and assemble with JDK9/Jigsaw See https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=361b902d0c01d9a2b82d4b126ecd3a228b955124 In fact only maven-javadoc-plugin is really required, all other plugins were already updated for other issues in 3.5.0 MNG-6127: Fix plugin execution configuration interference See https://git-wip-us.apache.org/repos/asf?p=maven-integration-testing.git;a=commit;h=82b043f8bd2015fc4ccac35df805ec2356100428 See https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=57e4b331ebd41ab5337c60a7c8fc4d3d435475fb MNG-6220: Add CLI options to control color output Fixed by introducing system property style.color=[auto*|always|never] See https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=fd57754218e749305be1dd745fda9407960cf985 thanks, Robert On Tue, 25 Apr 2017 22:43:54 +0200, Stephen Connolly wrote: I'd like people to take this next week to consider what issues we want to pull in scope for 3.5.1. If you are a committer, just add the issues to Fix Version of 3.5.1-candidate, ideally adding a comment at the same time with your reasoning. If once we have a seconding committer, they can just comment seconding and move the Fix Version to 3.5.1. I'm going to suggest a 1 week period of open scoping. After that point in time, my intent is to be more strict and apply "release manager risk management" on any new issues being targeted for 3.5.1. Similarly, if issues targeted for 3.5.1 are not making sufficient progress they will be dropped... but for now... it's open season! Get triaging! -Stephen - 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: [ANN] First call to round up issues for 3.5.1
I'm fine with that: style.color=[auto*|always|never] the original PR is still based on a CLI option which I don't like because all other style options are already and only controlled by system properties. I have to create a new branch if we can agree on this. Robert On Fri, 23 Jun 2017 16:34:55 +0200, Michael Osipov wrote: Am 2017-06-23 um 16:27 schrieb Robert Scholte: MNG-6220: Add CLI options to control color output by introducing system property style.color=[auto*|enabled|disabled] This definitively needs polish and a value style like tree/grep. I left several comments on the PR. - 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: [ANN] First call to round up issues for 3.5.1
Am 2017-06-23 um 16:27 schrieb Robert Scholte: MNG-6220: Add CLI options to control color output by introducing system property style.color=[auto*|enabled|disabled] This definitively needs polish and a value style like tree/grep. I left several comments on the PR. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [ANN] First call to round up issues for 3.5.1
Looking for someone who can second the following issues: MNG-6148: Can't package and assemble with JDK9/Jigsaw MNG-6127: Fix plugin execution configuration interference MNG-6220: Add CLI options to control color output by introducing system property style.color=[auto*|enabled|disabled] thanks, Robert On Tue, 25 Apr 2017 22:43:54 +0200, Stephen Connolly wrote: I'd like people to take this next week to consider what issues we want to pull in scope for 3.5.1. If you are a committer, just add the issues to Fix Version of 3.5.1-candidate, ideally adding a comment at the same time with your reasoning. If once we have a seconding committer, they can just comment seconding and move the Fix Version to 3.5.1. I'm going to suggest a 1 week period of open scoping. After that point in time, my intent is to be more strict and apply "release manager risk management" on any new issues being targeted for 3.5.1. Similarly, if issues targeted for 3.5.1 are not making sufficient progress they will be dropped... but for now... it's open season! Get triaging! -Stephen - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [ANN] First call to round up issues for 3.5.1
Hi Guillaume, +1 from me... for that fix.. Kind regards Karl Heinz Marbaise On 11/06/17 00:05, Guillaume Boué wrote: Hi, I'd like to propose MNG-6240 to be added in 3.5.1. Commit: http://git-wip-us.apache.org/repos/asf/maven/commit/e76e217a IT: http://git-wip-us.apache.org/repos/asf/maven-integration-testing/commit/a162291e Successful Jenkins build: https://builds.apache.org/job/maven-3.x-jenkinsfile/job/MNG-6240/ It fixes a regression introduced in the renaming of maven-aether-provider to maven-resolver-provider in 3.5.0. Maven Core only exports the org.apache.maven:maven-resolver-provider artifact for plugins, while it should also export org.apache.maven:maven-aether-provider for compatibility with plugins depending on older Maven versions. Thanks, Guillaume - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [ANN] First call to round up issues for 3.5.1
Hi, I'd like to propose MNG-6240 to be added in 3.5.1. Commit: http://git-wip-us.apache.org/repos/asf/maven/commit/e76e217a IT: http://git-wip-us.apache.org/repos/asf/maven-integration-testing/commit/a162291e Successful Jenkins build: https://builds.apache.org/job/maven-3.x-jenkinsfile/job/MNG-6240/ It fixes a regression introduced in the renaming of maven-aether-provider to maven-resolver-provider in 3.5.0. Maven Core only exports the org.apache.maven:maven-resolver-provider artifact for plugins, while it should also export org.apache.maven:maven-aether-provider for compatibility with plugins depending on older Maven versions. Thanks, Guillaume --- L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast. https://www.avast.com/antivirus - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [ANN] First call to round up issues for 3.5.1
Am 2017-06-04 um 20:55 schrieb Karl Heinz Marbaise: Hi, I would like to suggest to introduce: MNG-6206 MNG-6207 to be part of Maven 3.5.1... Currently for MNG-6206 we have a pull request which solves the issue also the IT's are Ok for this. I will check also for MNG-6207.. If there are no objections I will integrate them after the have been ready into master starting on tuesday ? +1 Both issues and PRs look fine to me. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [ANN] First call to round up issues for 3.5.1
Hi, I would like to suggest to introduce: MNG-6206 MNG-6207 to be part of Maven 3.5.1... Currently for MNG-6206 we have a pull request which solves the issue also the IT's are Ok for this. I will check also for MNG-6207.. If there are no objections I will integrate them after the have been ready into master starting on tuesday ? Kind regards Karl Heinz Marbaise - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [ANN] First call to round up issues for 3.5.1
This specific issue seems quite isolated to me and is likely introduced when switching from Sonetype Aether to Eclipse Aether, where (IIRC) the boolean became a Boolean. On Fri, 05 May 2017 22:18:11 +0200, Michael Osipov wrote: That wasn't actually my point. Christian wrote that to make the entire chain consistent several issues have to be addressed. Am 2017-05-05 um 21:54 schrieb Robert Scholte: AFAIK you, me and Stephen already agreed that MNG-5935 should be part of 3.5.1 On Fri, 05 May 2017 21:09:02 +0200, Michael Osipov wrote: We should consider this batch https://github.com/ChristianSchulte/maven/commit/3494c28426b8dd5711b730d622ba98d603caeda6#commitcomment-22009084 if we want to address the issue we talked about on IRC. Michael Am 2017-05-05 um 21:04 schrieb Robert Scholte: I gave my spin for the 3.5.1-candidates. I've mentioned the issues I'd like to add, but most are still waiting to be seconded. Robert On Fri, 05 May 2017 19:23:41 +0200, Stephen Connolly wrote: Progress seems to be being made... I'm willing to let current progress continue for the next 1-2 weeks before starting a whip-round to drive towards a release... anyone want me to accelerate? On Tue 25 Apr 2017 at 21:43, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: I'd like people to take this next week to consider what issues we want to pull in scope for 3.5.1. If you are a committer, just add the issues to Fix Version of 3.5.1-candidate, ideally adding a comment at the same time with your reasoning. If once we have a seconding committer, they can just comment seconding and move the Fix Version to 3.5.1. I'm going to suggest a 1 week period of open scoping. After that point in time, my intent is to be more strict and apply "release manager risk management" on any new issues being targeted for 3.5.1. Similarly, if issues targeted for 3.5.1 are not making sufficient progress they will be dropped... but for now... it's open season! Get triaging! -Stephen - 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 - 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: [ANN] First call to round up issues for 3.5.1
That wasn't actually my point. Christian wrote that to make the entire chain consistent several issues have to be addressed. Am 2017-05-05 um 21:54 schrieb Robert Scholte: AFAIK you, me and Stephen already agreed that MNG-5935 should be part of 3.5.1 On Fri, 05 May 2017 21:09:02 +0200, Michael Osipov wrote: We should consider this batch https://github.com/ChristianSchulte/maven/commit/3494c28426b8dd5711b730d622ba98d603caeda6#commitcomment-22009084 if we want to address the issue we talked about on IRC. Michael Am 2017-05-05 um 21:04 schrieb Robert Scholte: I gave my spin for the 3.5.1-candidates. I've mentioned the issues I'd like to add, but most are still waiting to be seconded. Robert On Fri, 05 May 2017 19:23:41 +0200, Stephen Connolly wrote: Progress seems to be being made... I'm willing to let current progress continue for the next 1-2 weeks before starting a whip-round to drive towards a release... anyone want me to accelerate? On Tue 25 Apr 2017 at 21:43, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: I'd like people to take this next week to consider what issues we want to pull in scope for 3.5.1. If you are a committer, just add the issues to Fix Version of 3.5.1-candidate, ideally adding a comment at the same time with your reasoning. If once we have a seconding committer, they can just comment seconding and move the Fix Version to 3.5.1. I'm going to suggest a 1 week period of open scoping. After that point in time, my intent is to be more strict and apply "release manager risk management" on any new issues being targeted for 3.5.1. Similarly, if issues targeted for 3.5.1 are not making sufficient progress they will be dropped... but for now... it's open season! Get triaging! -Stephen - 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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [ANN] First call to round up issues for 3.5.1
Hi, On 05/05/17 21:54, Robert Scholte wrote: AFAIK you, me and Stephen already agreed that MNG-5935 should be part of 3.5.1 +1 From me as well for this. Kind regards Karl Heinz Marbaise On Fri, 05 May 2017 21:09:02 +0200, Michael Osipov wrote: We should consider this batch https://github.com/ChristianSchulte/maven/commit/3494c28426b8dd5711b730d622ba98d603caeda6#commitcomment-22009084 if we want to address the issue we talked about on IRC. Michael Am 2017-05-05 um 21:04 schrieb Robert Scholte: I gave my spin for the 3.5.1-candidates. I've mentioned the issues I'd like to add, but most are still waiting to be seconded. Robert On Fri, 05 May 2017 19:23:41 +0200, Stephen Connolly wrote: Progress seems to be being made... I'm willing to let current progress continue for the next 1-2 weeks before starting a whip-round to drive towards a release... anyone want me to accelerate? On Tue 25 Apr 2017 at 21:43, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: I'd like people to take this next week to consider what issues we want to pull in scope for 3.5.1. If you are a committer, just add the issues to Fix Version of 3.5.1-candidate, ideally adding a comment at the same time with your reasoning. If once we have a seconding committer, they can just comment seconding and move the Fix Version to 3.5.1. I'm going to suggest a 1 week period of open scoping. After that point in time, my intent is to be more strict and apply "release manager risk management" on any new issues being targeted for 3.5.1. Similarly, if issues targeted for 3.5.1 are not making sufficient progress they will be dropped... but for now... it's open season! Get triaging! -Stephen - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [ANN] First call to round up issues for 3.5.1
AFAIK you, me and Stephen already agreed that MNG-5935 should be part of 3.5.1 On Fri, 05 May 2017 21:09:02 +0200, Michael Osipov wrote: We should consider this batch https://github.com/ChristianSchulte/maven/commit/3494c28426b8dd5711b730d622ba98d603caeda6#commitcomment-22009084 if we want to address the issue we talked about on IRC. Michael Am 2017-05-05 um 21:04 schrieb Robert Scholte: I gave my spin for the 3.5.1-candidates. I've mentioned the issues I'd like to add, but most are still waiting to be seconded. Robert On Fri, 05 May 2017 19:23:41 +0200, Stephen Connolly wrote: Progress seems to be being made... I'm willing to let current progress continue for the next 1-2 weeks before starting a whip-round to drive towards a release... anyone want me to accelerate? On Tue 25 Apr 2017 at 21:43, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: I'd like people to take this next week to consider what issues we want to pull in scope for 3.5.1. If you are a committer, just add the issues to Fix Version of 3.5.1-candidate, ideally adding a comment at the same time with your reasoning. If once we have a seconding committer, they can just comment seconding and move the Fix Version to 3.5.1. I'm going to suggest a 1 week period of open scoping. After that point in time, my intent is to be more strict and apply "release manager risk management" on any new issues being targeted for 3.5.1. Similarly, if issues targeted for 3.5.1 are not making sufficient progress they will be dropped... but for now... it's open season! Get triaging! -Stephen - 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: [ANN] First call to round up issues for 3.5.1
We should consider this batch https://github.com/ChristianSchulte/maven/commit/3494c28426b8dd5711b730d622ba98d603caeda6#commitcomment-22009084 if we want to address the issue we talked about on IRC. Michael Am 2017-05-05 um 21:04 schrieb Robert Scholte: I gave my spin for the 3.5.1-candidates. I've mentioned the issues I'd like to add, but most are still waiting to be seconded. Robert On Fri, 05 May 2017 19:23:41 +0200, Stephen Connolly wrote: Progress seems to be being made... I'm willing to let current progress continue for the next 1-2 weeks before starting a whip-round to drive towards a release... anyone want me to accelerate? On Tue 25 Apr 2017 at 21:43, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: I'd like people to take this next week to consider what issues we want to pull in scope for 3.5.1. If you are a committer, just add the issues to Fix Version of 3.5.1-candidate, ideally adding a comment at the same time with your reasoning. If once we have a seconding committer, they can just comment seconding and move the Fix Version to 3.5.1. I'm going to suggest a 1 week period of open scoping. After that point in time, my intent is to be more strict and apply "release manager risk management" on any new issues being targeted for 3.5.1. Similarly, if issues targeted for 3.5.1 are not making sufficient progress they will be dropped... but for now... it's open season! Get triaging! -Stephen - 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: [ANN] First call to round up issues for 3.5.1
I gave my spin for the 3.5.1-candidates. I've mentioned the issues I'd like to add, but most are still waiting to be seconded. Robert On Fri, 05 May 2017 19:23:41 +0200, Stephen Connolly wrote: Progress seems to be being made... I'm willing to let current progress continue for the next 1-2 weeks before starting a whip-round to drive towards a release... anyone want me to accelerate? On Tue 25 Apr 2017 at 21:43, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: I'd like people to take this next week to consider what issues we want to pull in scope for 3.5.1. If you are a committer, just add the issues to Fix Version of 3.5.1-candidate, ideally adding a comment at the same time with your reasoning. If once we have a seconding committer, they can just comment seconding and move the Fix Version to 3.5.1. I'm going to suggest a 1 week period of open scoping. After that point in time, my intent is to be more strict and apply "release manager risk management" on any new issues being targeted for 3.5.1. Similarly, if issues targeted for 3.5.1 are not making sufficient progress they will be dropped... but for now... it's open season! Get triaging! -Stephen - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [ANN] First call to round up issues for 3.5.1
Am 2017-05-05 um 19:23 schrieb Stephen Connolly: Progress seems to be being made... I'm willing to let current progress continue for the next 1-2 weeks before starting a whip-round to drive towards a release... anyone want me to accelerate? On Tue 25 Apr 2017 at 21:43, Stephen Connolly < No acceleration please, I'll need so time to get my stuff integrated. Especially because I found some flaws in our ITs and some regressions in some plugins. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [ANN] First call to round up issues for 3.5.1
Progress seems to be being made... I'm willing to let current progress continue for the next 1-2 weeks before starting a whip-round to drive towards a release... anyone want me to accelerate? On Tue 25 Apr 2017 at 21:43, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > I'd like people to take this next week to consider what issues we want to > pull in scope for 3.5.1. > > If you are a committer, just add the issues to Fix Version of > 3.5.1-candidate, ideally adding a comment at the same time with your > reasoning. > > If once we have a seconding committer, they can just comment seconding and > move the Fix Version to 3.5.1. > > I'm going to suggest a 1 week period of open scoping. After that point in > time, my intent is to be more strict and apply "release manager risk > management" on any new issues being targeted for 3.5.1. Similarly, if > issues targeted for 3.5.1 are not making sufficient progress they will be > dropped... but for now... it's open season! > > Get triaging! > > -Stephen > -- Sent from my phone
Re: [ANN] First call to round up issues for 3.5.1
Am 2017-05-02 um 14:13 schrieb Jon Harper: Hi, https://issues.apache.org/jira/browse/MNG-6184 (a.k.a. https://issues.apache.org/jira/browse/MNG-5592 ) still affects maven today. It's an old bug so the fix could be delayed, but it is relevant now because the bug is in the aether code that was migrated to the maven codebase in 3.5. I have closed the duplicate and reopened the original bug. On Mon, May 1, 2017 at 10:23 PM, Eric Lilja wrote: Is https://issues.apache.org/jira/browse/MNG-6025 being included in 3.5.1? I sure hope so! - Eric L On 2017-05-01 22:15, Hervé BOUTEMY wrote: great! I'll mark it for 3.5.1 Regards, Hervé Le lundi 1 mai 2017, 19:59:50 CEST Robert Scholte a écrit : @Hervé, I want to second MNG-6223 Robert On Tue, 25 Apr 2017 22:43:54 +0200, Stephen Connolly wrote: I'd like people to take this next week to consider what issues we want to pull in scope for 3.5.1. If you are a committer, just add the issues to Fix Version of 3.5.1-candidate, ideally adding a comment at the same time with your reasoning. If once we have a seconding committer, they can just comment seconding and move the Fix Version to 3.5.1. I'm going to suggest a 1 week period of open scoping. After that point in time, my intent is to be more strict and apply "release manager risk management" on any new issues being targeted for 3.5.1. Similarly, if issues targeted for 3.5.1 are not making sufficient progress they will be dropped... but for now... it's open season! Get triaging! -Stephen - 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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [ANN] First call to round up issues for 3.5.1
I've marked MNG-6025 as 3.5.1-candidate. It has been fixed before and looks like a nice improvement. Robert On Mon, 01 May 2017 22:23:35 +0200, Eric Lilja wrote: Is https://issues.apache.org/jira/browse/MNG-6025 being included in 3.5.1? I sure hope so! - Eric L On 2017-05-01 22:15, Hervé BOUTEMY wrote: great! I'll mark it for 3.5.1 Regards, Hervé Le lundi 1 mai 2017, 19:59:50 CEST Robert Scholte a écrit : @Hervé, I want to second MNG-6223 Robert On Tue, 25 Apr 2017 22:43:54 +0200, Stephen Connolly wrote: I'd like people to take this next week to consider what issues we want to pull in scope for 3.5.1. If you are a committer, just add the issues to Fix Version of 3.5.1-candidate, ideally adding a comment at the same time with your reasoning. If once we have a seconding committer, they can just comment seconding and move the Fix Version to 3.5.1. I'm going to suggest a 1 week period of open scoping. After that point in time, my intent is to be more strict and apply "release manager risk management" on any new issues being targeted for 3.5.1. Similarly, if issues targeted for 3.5.1 are not making sufficient progress they will be dropped... but for now... it's open season! Get triaging! -Stephen - 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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [ANN] First call to round up issues for 3.5.1
Hi, https://issues.apache.org/jira/browse/MNG-6184 (a.k.a. https://issues.apache.org/jira/browse/MNG-5592 ) still affects maven today. It's an old bug so the fix could be delayed, but it is relevant now because the bug is in the aether code that was migrated to the maven codebase in 3.5. Jon On Mon, May 1, 2017 at 10:23 PM, Eric Lilja wrote: > Is https://issues.apache.org/jira/browse/MNG-6025 being included in > 3.5.1? I sure hope so! > > - Eric L > > > On 2017-05-01 22:15, Hervé BOUTEMY wrote: > >> great! >> I'll mark it for 3.5.1 >> >> Regards, >> >> Hervé >> >> Le lundi 1 mai 2017, 19:59:50 CEST Robert Scholte a écrit : >> >>> @Hervé, I want to second MNG-6223 >>> >>> Robert >>> >>> On Tue, 25 Apr 2017 22:43:54 +0200, Stephen Connolly >>> >>> wrote: >>> I'd like people to take this next week to consider what issues we want to pull in scope for 3.5.1. If you are a committer, just add the issues to Fix Version of 3.5.1-candidate, ideally adding a comment at the same time with your reasoning. If once we have a seconding committer, they can just comment seconding and move the Fix Version to 3.5.1. I'm going to suggest a 1 week period of open scoping. After that point in time, my intent is to be more strict and apply "release manager risk management" on any new issues being targeted for 3.5.1. Similarly, if issues targeted for 3.5.1 are not making sufficient progress they will be dropped... but for now... it's open season! Get triaging! -Stephen >>> - >>> 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: [ANN] First call to round up issues for 3.5.1
Is https://issues.apache.org/jira/browse/MNG-6025 being included in 3.5.1? I sure hope so! - Eric L On 2017-05-01 22:15, Hervé BOUTEMY wrote: great! I'll mark it for 3.5.1 Regards, Hervé Le lundi 1 mai 2017, 19:59:50 CEST Robert Scholte a écrit : @Hervé, I want to second MNG-6223 Robert On Tue, 25 Apr 2017 22:43:54 +0200, Stephen Connolly wrote: I'd like people to take this next week to consider what issues we want to pull in scope for 3.5.1. If you are a committer, just add the issues to Fix Version of 3.5.1-candidate, ideally adding a comment at the same time with your reasoning. If once we have a seconding committer, they can just comment seconding and move the Fix Version to 3.5.1. I'm going to suggest a 1 week period of open scoping. After that point in time, my intent is to be more strict and apply "release manager risk management" on any new issues being targeted for 3.5.1. Similarly, if issues targeted for 3.5.1 are not making sufficient progress they will be dropped... but for now... it's open season! Get triaging! -Stephen - 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: [ANN] First call to round up issues for 3.5.1
great! I'll mark it for 3.5.1 Regards, Hervé Le lundi 1 mai 2017, 19:59:50 CEST Robert Scholte a écrit : > @Hervé, I want to second MNG-6223 > > Robert > > On Tue, 25 Apr 2017 22:43:54 +0200, Stephen Connolly > > wrote: > > I'd like people to take this next week to consider what issues we want to > > pull in scope for 3.5.1. > > > > If you are a committer, just add the issues to Fix Version of > > 3.5.1-candidate, ideally adding a comment at the same time with your > > reasoning. > > > > If once we have a seconding committer, they can just comment seconding > > and > > move the Fix Version to 3.5.1. > > > > I'm going to suggest a 1 week period of open scoping. After that point in > > time, my intent is to be more strict and apply "release manager risk > > management" on any new issues being targeted for 3.5.1. Similarly, if > > issues targeted for 3.5.1 are not making sufficient progress they will be > > dropped... but for now... it's open season! > > > > Get triaging! > > > > -Stephen > > - > 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: [ANN] First call to round up issues for 3.5.1
@Hervé, I want to second MNG-6223 Robert On Tue, 25 Apr 2017 22:43:54 +0200, Stephen Connolly wrote: I'd like people to take this next week to consider what issues we want to pull in scope for 3.5.1. If you are a committer, just add the issues to Fix Version of 3.5.1-candidate, ideally adding a comment at the same time with your reasoning. If once we have a seconding committer, they can just comment seconding and move the Fix Version to 3.5.1. I'm going to suggest a 1 week period of open scoping. After that point in time, my intent is to be more strict and apply "release manager risk management" on any new issues being targeted for 3.5.1. Similarly, if issues targeted for 3.5.1 are not making sufficient progress they will be dropped... but for now... it's open season! Get triaging! -Stephen - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Re: [ANN] First call to round up issues for 3.5.1
> Gesendet: Freitag, 28. April 2017 um 02:08 Uhr > Von: "Hervé BOUTEMY" > An: "Maven Developers List" > Betreff: Re: [ANN] First call to round up issues for 3.5.1 > > > * [MNG-6186] - switch to improved HawtJNI > > Robert: Improvements have not been accepted yet, branch now has conflicts > Guillaume Nodet, from Fusesource, has just merged > I don't know when he's considering to do a release, but it might be quite soon I have found another issue Guillaume fixed yesterday: https://github.com/fusesource/jansi/issues/83 > Le jeudi 27 avril 2017, 12:55:53 CEST Robert Scholte a écrit : > > Let me start going through the list of candidates: > > > > Maven - Version 3.5.1-candidate > > > > ** Sub-task > > * [MNG-6186] - switch to improved HawtJNI > > Robert: Improvements have not been accepted yet, branch now has conflicts > > > > > > ** Bug > > * [MNG-4347] - import-scoped dependencies of direct dependencies are > > not resolved using profile modifications from settings.xml > > Robert: Would like to postpone this. MRM must first be into place before > > we can create proper integration tests (case seems to be too complex for a > > unittest) > > > > * [MNG-4463] - Dependency management import should support version > > ranges. > > Robert: I wasn't aware that ranges are allowed here, but so it seems. We > > have a long list of depman issues, so maybe collect them for 3.6.x > > > > * [MNG-5359] - Declared execution in PluginMgmt gets bound to > > lifecycle (regression) > > Robert: Seems to be a huge commit, but worth investigating. IIUC this is > > only happening with plugins already bound the predefined lifecycles > > > > * [MNG-5527] - Dependency management import should support relocations. > > Robert: Seems valid > > > > * [MNG-5935] - Optional true getting lost in managed dependencies when > > transitive > > Robert: should be fixed > > > > * [MNG-5984] - Maven core extension resolution ignores repositories > > from activeByDefault profiles in settings.xml > > Robert: let's fix this, there's a patch, though not any test > > > > > > * [MNG-6112] - Central repository in the 4.0.0 super POM should > > declare update policy 'never'. > > Robert: Don't think we should fix this. > > > > * [MNG-6114] - Elements from the global settings should be ordered > > before elements from the user settings. > > Robert: In the end user settings should overwrite global settings. If this > > is not happening, we should fix this. > > > > * [MNG-6148] - Can't package and assemble with JDK9/Jigsaw > > Robert: easy fix, let's do so. > > > > * [MNG-6164] - Collections inconsistently immutable. > > Robert: maintenance with a valid argument. Let's fix this > > > > * [MNG-6188] - Console color not properly reset when interrupting > > build process > > Robert: I'm hitting this issue quite often (5-10% while interrupting a > > jetty:run). There doesn't seem to be a way to reproduce this for testing, > > because you are really killing the JVM. I think we should trust the > > shutdownhook. > > > > * [MNG-6216] - IndexArrayOutOfBounds when parsing POM > > Robert: requires a fix in Plexus-utils, but want to solve this. > > > > ** Improvement > > * [MNG-5457] - Show repository id when downloading or uploading > > from/to a remote repository > > Robert: Requires fix in Resolver, good for 3.5.1 > > > > * [MNG-5600] - Dependency management import should support exclusions. > > Robert: Worth fixing > > > > * [MNG-5639] - Support resolution of Import Scope POMs from Repo that > > contains a ${parameter} > > Robert: seems to be a complete patch: Let's fix this > > > > * [MNG-6069] - Migrate to non deprecated parts of Commons CLI > > Robert: Maintenance, let's fix this > > > > * [MNG-6169] - Lifecycle/binding plugin version updates > > Robert: Maintenance, let's fix this > > > > * [MNG-6206] - We should produce a WARNING by using RELEASE, LATEST as > > versions > > Maybe a warning is too aggressive. There can be other plugins which are > > capable to lock these versions before publishing, in which case it is not > > an issue. > > > > * [MNG-6207] - Create WARNINGs in case of using system scope > > Maybe a warning is too aggressive. In some cases there
Re: [ANN] First call to round up issues for 3.5.1
> * [MNG-6186] - switch to improved HawtJNI > Robert: Improvements have not been accepted yet, branch now has conflicts Guillaume Nodet, from Fusesource, has just merged I don't know when he's considering to do a release, but it might be quite soon Regards, Hervé Le jeudi 27 avril 2017, 12:55:53 CEST Robert Scholte a écrit : > Let me start going through the list of candidates: > > Maven - Version 3.5.1-candidate > > ** Sub-task > * [MNG-6186] - switch to improved HawtJNI > Robert: Improvements have not been accepted yet, branch now has conflicts > > > ** Bug > * [MNG-4347] - import-scoped dependencies of direct dependencies are > not resolved using profile modifications from settings.xml > Robert: Would like to postpone this. MRM must first be into place before > we can create proper integration tests (case seems to be too complex for a > unittest) > > * [MNG-4463] - Dependency management import should support version > ranges. > Robert: I wasn't aware that ranges are allowed here, but so it seems. We > have a long list of depman issues, so maybe collect them for 3.6.x > > * [MNG-5359] - Declared execution in PluginMgmt gets bound to > lifecycle (regression) > Robert: Seems to be a huge commit, but worth investigating. IIUC this is > only happening with plugins already bound the predefined lifecycles > > * [MNG-5527] - Dependency management import should support relocations. > Robert: Seems valid > > * [MNG-5935] - Optional true getting lost in managed dependencies when > transitive > Robert: should be fixed > > * [MNG-5984] - Maven core extension resolution ignores repositories > from activeByDefault profiles in settings.xml > Robert: let's fix this, there's a patch, though not any test > > > * [MNG-6112] - Central repository in the 4.0.0 super POM should > declare update policy 'never'. > Robert: Don't think we should fix this. > > * [MNG-6114] - Elements from the global settings should be ordered > before elements from the user settings. > Robert: In the end user settings should overwrite global settings. If this > is not happening, we should fix this. > > * [MNG-6148] - Can't package and assemble with JDK9/Jigsaw > Robert: easy fix, let's do so. > > * [MNG-6164] - Collections inconsistently immutable. > Robert: maintenance with a valid argument. Let's fix this > > * [MNG-6188] - Console color not properly reset when interrupting > build process > Robert: I'm hitting this issue quite often (5-10% while interrupting a > jetty:run). There doesn't seem to be a way to reproduce this for testing, > because you are really killing the JVM. I think we should trust the > shutdownhook. > > * [MNG-6216] - IndexArrayOutOfBounds when parsing POM > Robert: requires a fix in Plexus-utils, but want to solve this. > > ** Improvement > * [MNG-5457] - Show repository id when downloading or uploading > from/to a remote repository > Robert: Requires fix in Resolver, good for 3.5.1 > > * [MNG-5600] - Dependency management import should support exclusions. > Robert: Worth fixing > > * [MNG-5639] - Support resolution of Import Scope POMs from Repo that > contains a ${parameter} > Robert: seems to be a complete patch: Let's fix this > > * [MNG-6069] - Migrate to non deprecated parts of Commons CLI > Robert: Maintenance, let's fix this > > * [MNG-6169] - Lifecycle/binding plugin version updates > Robert: Maintenance, let's fix this > > * [MNG-6206] - We should produce a WARNING by using RELEASE, LATEST as > versions > Maybe a warning is too aggressive. There can be other plugins which are > capable to lock these versions before publishing, in which case it is not > an issue. > > * [MNG-6207] - Create WARNINGs in case of using system scope > Maybe a warning is too aggressive. In some cases there's simply no other > solution, like referring to tools.jar. > > > ** New Feature > * [MNG-6220] - Add CLI options to control color output > Robert: If we agree on the system property (just like changing the > colors), then yes. > > > ** Task > * [MNG-2893] - Update the DefaultPluginManager to not use a project > depMan for controlling it's transitive dependencies > Robert: Description is minimal, but seems to make sense. > > * [MNG-6167] - Clean up dependency mess (reported by > dependency:analyze) > Robert: Maintenance, let's fix this. > > > > > On Tue, 25 Apr 2017 22:43:54 +0200, Stephen Connolly > > wrote: > > I'd like people to take this next week to consider what issues we want to > > pull in scope for 3.5.1. > > > > If you are a committer, just add the issues to Fix Version of > > 3.5.1-candidate, ideally adding a comment at the same time with your > > reasoning. > > > > If once we have a seconding committer, they can just comment seconding > > and > > move the Fix Version to 3.5.1. > > > > I'm going to suggest a 1 week period of open scoping. After that point in > > time, my
Re: [ANN] First call to round up issues for 3.5.1
Hi, I would like to add the following issue: MNG-6123 - detect self references in POM and fail fast Karl Heinz: Currently having an implementation but currently conflicts with some IT's cause they are using self referencing dependencies. Moved it to "3.5.1-candidate"... Kind regards Karl Heinz On 27/04/17 12:55, Robert Scholte wrote: Let me start going through the list of candidates: Maven - Version 3.5.1-candidate ** Sub-task * [MNG-6186] - switch to improved HawtJNI Robert: Improvements have not been accepted yet, branch now has conflicts ** Bug * [MNG-4347] - import-scoped dependencies of direct dependencies are not resolved using profile modifications from settings.xml Robert: Would like to postpone this. MRM must first be into place before we can create proper integration tests (case seems to be too complex for a unittest) * [MNG-4463] - Dependency management import should support version ranges. Robert: I wasn't aware that ranges are allowed here, but so it seems. We have a long list of depman issues, so maybe collect them for 3.6.x * [MNG-5359] - Declared execution in PluginMgmt gets bound to lifecycle (regression) Robert: Seems to be a huge commit, but worth investigating. IIUC this is only happening with plugins already bound the predefined lifecycles * [MNG-5527] - Dependency management import should support relocations. Robert: Seems valid * [MNG-5935] - Optional true getting lost in managed dependencies when transitive Robert: should be fixed * [MNG-5984] - Maven core extension resolution ignores repositories from activeByDefault profiles in settings.xml Robert: let's fix this, there's a patch, though not any test * [MNG-6112] - Central repository in the 4.0.0 super POM should declare update policy 'never'. Robert: Don't think we should fix this. * [MNG-6114] - Elements from the global settings should be ordered before elements from the user settings. Robert: In the end user settings should overwrite global settings. If this is not happening, we should fix this. * [MNG-6148] - Can't package and assemble with JDK9/Jigsaw Robert: easy fix, let's do so. * [MNG-6164] - Collections inconsistently immutable. Robert: maintenance with a valid argument. Let's fix this * [MNG-6188] - Console color not properly reset when interrupting build process Robert: I'm hitting this issue quite often (5-10% while interrupting a jetty:run). There doesn't seem to be a way to reproduce this for testing, because you are really killing the JVM. I think we should trust the shutdownhook. * [MNG-6216] - IndexArrayOutOfBounds when parsing POM Robert: requires a fix in Plexus-utils, but want to solve this. ** Improvement * [MNG-5457] - Show repository id when downloading or uploading from/to a remote repository Robert: Requires fix in Resolver, good for 3.5.1 * [MNG-5600] - Dependency management import should support exclusions. Robert: Worth fixing * [MNG-5639] - Support resolution of Import Scope POMs from Repo that contains a ${parameter} Robert: seems to be a complete patch: Let's fix this * [MNG-6069] - Migrate to non deprecated parts of Commons CLI Robert: Maintenance, let's fix this * [MNG-6169] - Lifecycle/binding plugin version updates Robert: Maintenance, let's fix this * [MNG-6206] - We should produce a WARNING by using RELEASE, LATEST as versions Maybe a warning is too aggressive. There can be other plugins which are capable to lock these versions before publishing, in which case it is not an issue. * [MNG-6207] - Create WARNINGs in case of using system scope Maybe a warning is too aggressive. In some cases there's simply no other solution, like referring to tools.jar. ** New Feature * [MNG-6220] - Add CLI options to control color output Robert: If we agree on the system property (just like changing the colors), then yes. ** Task * [MNG-2893] - Update the DefaultPluginManager to not use a project depMan for controlling it's transitive dependencies Robert: Description is minimal, but seems to make sense. * [MNG-6167] - Clean up dependency mess (reported by dependency:analyze) Robert: Maintenance, let's fix this. On Tue, 25 Apr 2017 22:43:54 +0200, Stephen Connolly wrote: I'd like people to take this next week to consider what issues we want to pull in scope for 3.5.1. If you are a committer, just add the issues to Fix Version of 3.5.1-candidate, ideally adding a comment at the same time with your reasoning. If once we have a seconding committer, they can just comment seconding and move the Fix Version to 3.5.1. I'm going to suggest a 1 week period of open scoping. After that point in time, my intent is to be more strict and apply "release manager risk management" on any new issues being targeted for 3.5.1. Similarly, if issues targeted for 3.5.1 are not making sufficient progress they will be dropped... but for now... it's open season! Get triaging! -Stephen --
Re: [ANN] First call to round up issues for 3.5.1
Some of them are assigned to me. I won't make it before Wednesday but like to address them in 3.5.1. Michael Am 2017-04-27 um 12:55 schrieb Robert Scholte: Let me start going through the list of candidates: Maven - Version 3.5.1-candidate ** Sub-task * [MNG-6186] - switch to improved HawtJNI Robert: Improvements have not been accepted yet, branch now has conflicts ** Bug * [MNG-4347] - import-scoped dependencies of direct dependencies are not resolved using profile modifications from settings.xml Robert: Would like to postpone this. MRM must first be into place before we can create proper integration tests (case seems to be too complex for a unittest) * [MNG-4463] - Dependency management import should support version ranges. Robert: I wasn't aware that ranges are allowed here, but so it seems. We have a long list of depman issues, so maybe collect them for 3.6.x * [MNG-5359] - Declared execution in PluginMgmt gets bound to lifecycle (regression) Robert: Seems to be a huge commit, but worth investigating. IIUC this is only happening with plugins already bound the predefined lifecycles * [MNG-5527] - Dependency management import should support relocations. Robert: Seems valid * [MNG-5935] - Optional true getting lost in managed dependencies when transitive Robert: should be fixed * [MNG-5984] - Maven core extension resolution ignores repositories from activeByDefault profiles in settings.xml Robert: let's fix this, there's a patch, though not any test * [MNG-6112] - Central repository in the 4.0.0 super POM should declare update policy 'never'. Robert: Don't think we should fix this. * [MNG-6114] - Elements from the global settings should be ordered before elements from the user settings. Robert: In the end user settings should overwrite global settings. If this is not happening, we should fix this. * [MNG-6148] - Can't package and assemble with JDK9/Jigsaw Robert: easy fix, let's do so. * [MNG-6164] - Collections inconsistently immutable. Robert: maintenance with a valid argument. Let's fix this * [MNG-6188] - Console color not properly reset when interrupting build process Robert: I'm hitting this issue quite often (5-10% while interrupting a jetty:run). There doesn't seem to be a way to reproduce this for testing, because you are really killing the JVM. I think we should trust the shutdownhook. * [MNG-6216] - IndexArrayOutOfBounds when parsing POM Robert: requires a fix in Plexus-utils, but want to solve this. ** Improvement * [MNG-5457] - Show repository id when downloading or uploading from/to a remote repository Robert: Requires fix in Resolver, good for 3.5.1 * [MNG-5600] - Dependency management import should support exclusions. Robert: Worth fixing * [MNG-5639] - Support resolution of Import Scope POMs from Repo that contains a ${parameter} Robert: seems to be a complete patch: Let's fix this * [MNG-6069] - Migrate to non deprecated parts of Commons CLI Robert: Maintenance, let's fix this * [MNG-6169] - Lifecycle/binding plugin version updates Robert: Maintenance, let's fix this * [MNG-6206] - We should produce a WARNING by using RELEASE, LATEST as versions Maybe a warning is too aggressive. There can be other plugins which are capable to lock these versions before publishing, in which case it is not an issue. * [MNG-6207] - Create WARNINGs in case of using system scope Maybe a warning is too aggressive. In some cases there's simply no other solution, like referring to tools.jar. ** New Feature * [MNG-6220] - Add CLI options to control color output Robert: If we agree on the system property (just like changing the colors), then yes. ** Task * [MNG-2893] - Update the DefaultPluginManager to not use a project depMan for controlling it's transitive dependencies Robert: Description is minimal, but seems to make sense. * [MNG-6167] - Clean up dependency mess (reported by dependency:analyze) Robert: Maintenance, let's fix this. On Tue, 25 Apr 2017 22:43:54 +0200, Stephen Connolly wrote: I'd like people to take this next week to consider what issues we want to pull in scope for 3.5.1. If you are a committer, just add the issues to Fix Version of 3.5.1-candidate, ideally adding a comment at the same time with your reasoning. If once we have a seconding committer, they can just comment seconding and move the Fix Version to 3.5.1. I'm going to suggest a 1 week period of open scoping. After that point in time, my intent is to be more strict and apply "release manager risk management" on any new issues being targeted for 3.5.1. Similarly, if issues targeted for 3.5.1 are not making sufficient progress they will be dropped... but for now... it's open season! Get triaging! -Stephen - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [ANN] First call to round up issues for 3.5.1
Let me start going through the list of candidates: Maven - Version 3.5.1-candidate ** Sub-task * [MNG-6186] - switch to improved HawtJNI Robert: Improvements have not been accepted yet, branch now has conflicts ** Bug * [MNG-4347] - import-scoped dependencies of direct dependencies are not resolved using profile modifications from settings.xml Robert: Would like to postpone this. MRM must first be into place before we can create proper integration tests (case seems to be too complex for a unittest) * [MNG-4463] - Dependency management import should support version ranges. Robert: I wasn't aware that ranges are allowed here, but so it seems. We have a long list of depman issues, so maybe collect them for 3.6.x * [MNG-5359] - Declared execution in PluginMgmt gets bound to lifecycle (regression) Robert: Seems to be a huge commit, but worth investigating. IIUC this is only happening with plugins already bound the predefined lifecycles * [MNG-5527] - Dependency management import should support relocations. Robert: Seems valid * [MNG-5935] - Optional true getting lost in managed dependencies when transitive Robert: should be fixed * [MNG-5984] - Maven core extension resolution ignores repositories from activeByDefault profiles in settings.xml Robert: let's fix this, there's a patch, though not any test * [MNG-6112] - Central repository in the 4.0.0 super POM should declare update policy 'never'. Robert: Don't think we should fix this. * [MNG-6114] - Elements from the global settings should be ordered before elements from the user settings. Robert: In the end user settings should overwrite global settings. If this is not happening, we should fix this. * [MNG-6148] - Can't package and assemble with JDK9/Jigsaw Robert: easy fix, let's do so. * [MNG-6164] - Collections inconsistently immutable. Robert: maintenance with a valid argument. Let's fix this * [MNG-6188] - Console color not properly reset when interrupting build process Robert: I'm hitting this issue quite often (5-10% while interrupting a jetty:run). There doesn't seem to be a way to reproduce this for testing, because you are really killing the JVM. I think we should trust the shutdownhook. * [MNG-6216] - IndexArrayOutOfBounds when parsing POM Robert: requires a fix in Plexus-utils, but want to solve this. ** Improvement * [MNG-5457] - Show repository id when downloading or uploading from/to a remote repository Robert: Requires fix in Resolver, good for 3.5.1 * [MNG-5600] - Dependency management import should support exclusions. Robert: Worth fixing * [MNG-5639] - Support resolution of Import Scope POMs from Repo that contains a ${parameter} Robert: seems to be a complete patch: Let's fix this * [MNG-6069] - Migrate to non deprecated parts of Commons CLI Robert: Maintenance, let's fix this * [MNG-6169] - Lifecycle/binding plugin version updates Robert: Maintenance, let's fix this * [MNG-6206] - We should produce a WARNING by using RELEASE, LATEST as versions Maybe a warning is too aggressive. There can be other plugins which are capable to lock these versions before publishing, in which case it is not an issue. * [MNG-6207] - Create WARNINGs in case of using system scope Maybe a warning is too aggressive. In some cases there's simply no other solution, like referring to tools.jar. ** New Feature * [MNG-6220] - Add CLI options to control color output Robert: If we agree on the system property (just like changing the colors), then yes. ** Task * [MNG-2893] - Update the DefaultPluginManager to not use a project depMan for controlling it's transitive dependencies Robert: Description is minimal, but seems to make sense. * [MNG-6167] - Clean up dependency mess (reported by dependency:analyze) Robert: Maintenance, let's fix this. On Tue, 25 Apr 2017 22:43:54 +0200, Stephen Connolly wrote: I'd like people to take this next week to consider what issues we want to pull in scope for 3.5.1. If you are a committer, just add the issues to Fix Version of 3.5.1-candidate, ideally adding a comment at the same time with your reasoning. If once we have a seconding committer, they can just comment seconding and move the Fix Version to 3.5.1. I'm going to suggest a 1 week period of open scoping. After that point in time, my intent is to be more strict and apply "release manager risk management" on any new issues being targeted for 3.5.1. Similarly, if issues targeted for 3.5.1 are not making sufficient progress they will be dropped... but for now... it's open season! Get triaging! -Stephen - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org