Re: [DISCUSS] Big Scrub for proposed 3.5.0 (if we reset master)

Le jeudi 5 janvier 2017, 22:40:10 CET Robert Scholte a écrit : > Hervé Boutemy: > It seems that all issues have to do with expanding URLs and connections. yes, calculating effective values for each pom > Right now there's business logic in the ModelBuilder to calculate such > values. We already

Re: [DISCUSS] Big Scrub for proposed 3.5.0 (if we reset master)

Regarding the proposed changes: Stephen Connolly: MNG-5823 - mvnDebug doesn't work with M2_HOME with spaces - missing quotes is this one superseded by MNG-5607? MNG-5837 - Syntax error in bin/mvn on Solaris SPARC Cannot confirm MNG-5904 - Remove the whole Ant Build I'd say 3.5.1 MNG-5967 -

Re: [DISCUSS] Big Scrub for proposed 3.5.0 (if we reset master)

Am 2017-01-04 um 10:06 schrieb Stephen Connolly: On 31 December 2016 at 20:10, Stephen Connolly I have updated the tracking of these issues previously without a JIRA: MNG- WONTFIX Removing redundant test This is part of MNG-5977 MNG- WONTFIX updated code to

Re: [DISCUSS] Big Scrub for proposed 3.5.0 (if we reset master)

On 31 December 2016 at 20:10, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > MNG- WONTFIX Add a ProjectArtifactsCache similar to > PluginArtifactsCache > MNG- WONTFIX added core extensions documentation > MNG- WONTFIX

Re: [DISCUSS] Big Scrub for proposed 3.5.0 (if we reset master)

Seconded on both I'll update the wiki page tomorrow On Tue 3 Jan 2017 at 21:44, Michael Osipov wrote: > Am 2017-01-02 um 21:34 schrieb Stephen Connolly: > > > On 2 January 2017 at 20:15, Michael Osipov wrote: > > > > > MNG-6029, > > > > >

Re: [DISCUSS] Big Scrub for proposed 3.5.0 (if we reset master)

Am 01/03/17 um 14:55 schrieb Robert Scholte: > Unscrubbed: > MNG-5670 - ConcurrentModificationException during > DefaultMaven.newRepositorySession This is related to MNG-6053 and MNG-6105. You can see that there is a commit @MNG-6105 touching 'MavenRepositorySystemUtils' as well. Should be

Re: [DISCUSS] Big Scrub for proposed 3.5.0 (if we reset master)

Am 2017-01-02 um 21:34 schrieb Stephen Connolly: On 2 January 2017 at 20:15, Michael Osipov wrote: MNG-6029, I'd second this for 3.5.1 I have concerns with introducing for 3.5.0 as it affects how the classpath gets built and could cause behaviour differences between

Re: [DISCUSS] Big Scrub for proposed 3.5.0 (if we reset master)

MNG- WONTFIX upgrade m-assembly-p to 3.0.0 Created MNG-6148 for this. There are more plugins effected by this, but I guess these were updated in the general "update plugins" ticket. IMO we should bind all plugin updates required for Java9 to this issue. For me M3.5.1 is good

Re: [DISCUSS] Big Scrub for proposed 3.5.0 (if we reset master)

Am 2017-01-03 um 15:19 schrieb Stephen Connolly: https://cwiki.apache.org/confluence/display/MAVEN/Roadmap+2017 is updated with these scope changes. We still have 24 JIRAs under consideration... plus we need to decide on the commits that do not have a JIRA For my issue-less commits:

Re: [DISCUSS] Big Scrub for proposed 3.5.0 (if we reset master)

https://cwiki.apache.org/confluence/display/MAVEN/Roadmap+2017 is updated with these scope changes. We still have 24 JIRAs under consideration... plus we need to decide on the commits that do not have a JIRA On Tue, 3 Jan 2017 at 13:55 Robert Scholte wrote: > Just to

Re: [DISCUSS] Big Scrub for proposed 3.5.0 (if we reset master)

Just to confirm: I agree on the "Agreed changes" too I'd like to add for 3.5.0: By Stephen: MNG-5824 - Support MAVEN_ARGS environment variable as a way of supplying default command line arguments MNG-5836 - logging config is overwritten by $M2_HOME/lib/ext/*.jar MNG-5946 - Fix links etc. in

Re: [DISCUSS] Big Scrub for proposed 3.5.0 (if we reset master)

FIX-3.5.0: MNG-5889 .mvn directory should be picked when using --file seconded Regards, Hervé Le samedi 31 décembre 2016, 21:14:59 CET Stephen Connolly a écrit : > FIX-3.5.0: MNG-5607, MNG-5815, MNG-5823, MNG-5824, MNG-5836, MNG-5837, > MNG-5889, MNG-5904, MNG-5946, MNG-5963, MNG-5967,

Re: [DISCUSS] Big Scrub for proposed 3.5.0 (if we reset master)

looking for seconds on new features related to site url calculations: MNG-4508 - No way to avoid adding artifactId to site urls MNG-5878 - add support for module name != artifactId in every calculated URLs (project, SCM, site): special project.directory property MNG-5951 - add an option to avoid

Re: [DISCUSS] Big Scrub for proposed 3.5.0 (if we reset master)

in general, I completely agree in this specific case, where there were changes in 1.1.0 and 1.2.0-SNAPSHOT that we won't integrate yet, Aether 1.0.2 followed by Artifact Resolver 1.0.3 with only coordinate changes (but not code) seems easier to understand Regards, Hervé Le lundi 2 janvier

Re: [DISCUSS] Big Scrub for proposed 3.5.0 (if we reset master)

On Monday, 2 January 2017, Michael Osipov wrote: > Am 2017-01-02 um 21:34 schrieb Stephen Connolly: > >> On 2 January 2017 at 20:15, Michael Osipov wrote: >> >> Am 2017-01-02 um 20:35 schrieb Stephen Connolly: >>> >>> On 2 January 2017 at 18:49, Michael

Re: [DISCUSS] Big Scrub for proposed 3.5.0 (if we reset master)

Am 2017-01-02 um 21:34 schrieb Stephen Connolly: On 2 January 2017 at 20:15, Michael Osipov wrote: Am 2017-01-02 um 20:35 schrieb Stephen Connolly: On 2 January 2017 at 18:49, Michael Osipov wrote: Am 2017-01-01 um 15:51 schrieb Stephen Connolly:

Re: [DISCUSS] Big Scrub for proposed 3.5.0 (if we reset master)

On 2 January 2017 at 20:34, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > > > On 2 January 2017 at 20:15, Michael Osipov wrote: > >> Am 2017-01-02 um 20:35 schrieb Stephen Connolly: >> >>> On 2 January 2017 at 18:49, Michael Osipov wrote:

Re: [DISCUSS] Big Scrub for proposed 3.5.0 (if we reset master)

On 2 January 2017 at 20:15, Michael Osipov wrote: > Am 2017-01-02 um 20:35 schrieb Stephen Connolly: > >> On 2 January 2017 at 18:49, Michael Osipov wrote: >> >> Am 2017-01-01 um 15:51 schrieb Stephen Connolly: >>> >>> On 1 January 2017 at 00:55,

Re: [DISCUSS] Big Scrub for proposed 3.5.0 (if we reset master)

On Mon, 02 Jan 2017 21:04:57 +0100, Stephen Connolly wrote: On 31 December 2016 at 20:10, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: Here are the changes in current master since 3.3.9 (with some minor changes omitted) Issue ID Target

Re: [DISCUSS] Big Scrub for proposed 3.5.0 (if we reset master)

Am 2017-01-02 um 20:35 schrieb Stephen Connolly: On 2 January 2017 at 18:49, Michael Osipov wrote: Am 2017-01-01 um 15:51 schrieb Stephen Connolly: On 1 January 2017 at 00:55, Michael Osipov wrote: I just went through the list my issues. Here is a

Re: [DISCUSS] Big Scrub for proposed 3.5.0 (if we reset master)

On 31 December 2016 at 20:10, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > Here are the changes in current master since 3.3.9 (with some minor > changes omitted) > > Issue ID Target Version Summary > == >

Re: [DISCUSS] Big Scrub for proposed 3.5.0 (if we reset master)

On 2 January 2017 at 18:49, Michael Osipov wrote: > Am 2017-01-01 um 15:51 schrieb Stephen Connolly: > >> On 1 January 2017 at 00:55, Michael Osipov wrote: >> >> I just went through the list my issues. Here is a safe list I would >>> merge/cherry-pick

Re: [DISCUSS] Big Scrub for proposed 3.5.0 (if we reset master)

Am 2017-01-01 um 18:44 schrieb Guillaume Boué: This is the list of JIRA issues that targets colourised logging / are related to it: MNG-3507 ANSI color logging for improved output visibilityThis is the root JIRA issue. MNG-3705 Expression: ${executedProject} doesn't work in reports

Re: [DISCUSS] Big Scrub for proposed 3.5.0 (if we reset master)

Am 2017-01-01 um 18:44 schrieb Guillaume Boué: Le 01/01/2017 à 01:55, Michael Osipov a écrit : I just went through the list my issues. Here is a safe list I would merge/cherry-pick into new master: FIX-3.5.0: MNG-5457, Note: this is dependant upon MRESOLVER-2 (commit

Re: [DISCUSS] Big Scrub for proposed 3.5.0 (if we reset master)

Am 2017-01-01 um 15:51 schrieb Stephen Connolly: On 1 January 2017 at 00:55, Michael Osipov wrote: I just went through the list my issues. Here is a safe list I would merge/cherry-pick into new master: FIX-3.5.0: MNG-5567, Affects behaviour, I recommend 3.5.1 but I

Re: [DISCUSS] Big Scrub for proposed 3.5.0 (if we reset master)

You should be able to edit. If not ping Hervé Yes there are changes between 3.2.x and 3.3.9, what we want from 3.5.0 is to make the only behaviour change be a no-op for switching aether for resolver... after that 3.5.1 can fix bugs On Sun 1 Jan 2017 at 22:52, Christian Schulte

Re: [DISCUSS] Big Scrub for proposed 3.5.0 (if we reset master)

OK, thanks for confirming this. Le 01/01/2017 à 23:44, Christian Schulte a écrit : Am 01/01/17 um 18:44 schrieb Guillaume Boué: There is a commit about MRESOLVER-9 in tag 2.11 of Wagon:

Re: [DISCUSS] Big Scrub for proposed 3.5.0 (if we reset master)

Am 01/01/17 um 16:09 schrieb Stephen Connolly: > If you want to know the current status check > https://cwiki.apache.org/confluence/display/MAVEN/Roadmap+2017 Can I edit that page myself? User name is "schulte". Regarding the drop in replacement for 3.3.9: MNG-2199 was already working in Maven

Re: [DISCUSS] Big Scrub for proposed 3.5.0 (if we reset master)

Am 01/01/17 um 18:44 schrieb Guillaume Boué: > > There is a commit about MRESOLVER-9 in tag 2.11 of Wagon: > https://git1-us-west.apache.org/repos/asf?p=maven-wagon.git;a=commit;h=f244ece2eee01500e4b1bc334b8dcd35b47f9422. > > I'm unsure whether it is safe to use this tag if MRESOLVER-9 doesn't

Re: [DISCUSS] Big Scrub for proposed 3.5.0 (if we reset master)

Le dimanche 1 janvier 2017, 18:44:52 CET Guillaume Boué a écrit : > This is the list of JIRA issues that targets colourised logging / are > related to it: > > MNG-3507 ANSI color logging for improved output visibility This is > the > root JIRA issue. +1 > MNG-3705 Expression:

Re: [DISCUSS] Big Scrub for proposed 3.5.0 (if we reset master)

This is the list of JIRA issues that targets colourised logging / are related to it: MNG-3507ANSI color logging for improved output visibility This is the root JIRA issue. MNG-3705Expression: ${executedProject} doesn't work in reports SVN revisions

Re: [DISCUSS] Big Scrub for proposed 3.5.0 (if we reset master)

Le 01/01/2017 à 01:55, Michael Osipov a écrit : I just went through the list my issues. Here is a safe list I would merge/cherry-pick into new master: FIX-3.5.0: MNG-5457, Note: this is dependant upon MRESOLVER-2 (commit

Re: [DISCUSS] Big Scrub for proposed 3.5.0 (if we reset master)

If you want to know the current status check https://cwiki.apache.org/confluence/display/MAVEN/Roadmap+2017 On 31 December 2016 at 20:10, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > Here are the changes in current master since 3.3.9 (with some minor > changes omitted) > > Issue

Re: [DISCUSS] Big Scrub for proposed 3.5.0 (if we reset master)

On 1 January 2017 at 04:42, Christian Schulte wrote: > Am 12/31/16 um 21:10 schrieb Stephen Connolly: > > Here are the changes in current master since 3.3.9 (with some minor > changes > > omitted) > > > > Issue ID Target Version Summary > > ==

Re: [DISCUSS] Big Scrub for proposed 3.5.0 (if we reset master)

On 1 January 2017 at 00:55, Michael Osipov wrote: > I just went through the list my issues. Here is a safe list I would > merge/cherry-pick into new master: > > FIX-3.5.0: > MNG-5457, Should not affect behaviour: I'll second > MNG-5567, Affects behaviour, I

Re: [DISCUSS] Big Scrub for proposed 3.5.0 (if we reset master)

MNG-5962: I'll second that one MNG-5958: I think this one is debatable as it stops 3.5.0 from being a drop-in behaviour replacement of 3.3.9, but I don't feel strongly enough to push it to 3.5.1 MNG-6117: Ditto for 5958, you'll need somebody to second this one for 3.5.0. I'll second it for 3.5.1

Re: [DISCUSS] Big Scrub for proposed 3.5.0 (if we reset master)

Am 2017-01-01 um 10:26 schrieb Stephen Connolly: On 1 January 2017 at 00:55, Michael Osipov wrote: MNG-5963, MNG-6137 I couldn't find them in my list... note to self, double check... note to michael, can you confirm I distilled from your list, filtered git log and

Re: [DISCUSS] Big Scrub for proposed 3.5.0 (if we reset master)

Am 2017-01-01 um 04:51 schrieb Christian Schulte: Am 01/01/17 um 01:55 schrieb Michael Osipov: Undecided: MNG-5708: fixed by Christian's work Should not be done in that release. Let's ship all bugfixes affecting resolution together - not just one after the other. All or nothing. So nothing.

Re: [DISCUSS] Big Scrub for proposed 3.5.0 (if we reset master)

On 1 January 2017 at 00:55, Michael Osipov wrote: > MNG-5963, MNG-6137 I couldn't find them in my list... note to self, double check... note to michael, can you confirm Otherwise I have updated the wiki with your proposals (some of which were seconds and moved things

Re: [DISCUSS] Big Scrub for proposed 3.5.0 (if we reset master)

We cannot update the JIRA issues until after we do the reset On 1 January 2017 at 04:51, Christian Schulte wrote: > I think it would be easier if we just update the JIRA issues and set the > version the issue will be shipped in. We already have a 3.5.0 version > available. That

Re: [DISCUSS] Big Scrub for proposed 3.5.0 (if we reset master)

What I marked FIX-3.6.0 could also be marked FIX-4.0.0. I cannot tell. I would have made it part of 3.4.0 so better someone else decides that. Am 01/01/17 um 05:42 schrieb Christian Schulte: > Am 12/31/16 um 21:10 schrieb Stephen Connolly: >> Here are the changes in current master since 3.3.9

Re: [DISCUSS] Big Scrub for proposed 3.5.0 (if we reset master)

I think it would be easier if we just update the JIRA issues and set the version the issue will be shipped in. We already have a 3.5.0 version available. That will be the next Maven release? So we would need a 3.6.0 version and a 4.0.0 version and a 5.0.0 version. Let 4.0.0 be the next major

Re: [DISCUSS] Big Scrub for proposed 3.5.0 (if we reset master)

Am 12/31/16 um 21:10 schrieb Stephen Connolly: > Here are the changes in current master since 3.3.9 (with some minor changes > omitted) > > Issue ID Target Version Summary > == > MNG-1577 WONTFIX

Re: [DISCUSS] Big Scrub for proposed 3.5.0 (if we reset master)

Am 12/31/16 um 22:14 schrieb Stephen Connolly: > FIX-3.5.0: MNG-5607, MNG-5815, MNG-5823, MNG-5824, MNG-5836, MNG-5837, > MNG-5889, MNG-5904, MNG-5946, MNG-5963, MNG-5967, MNG-5968, MNG-6001, > MNG-6003, MNG-6078 MNG-5968 will require updates to the ITs due to the maven-plugin-plugin no longer

Re: [DISCUSS] Big Scrub for proposed 3.5.0 (if we reset master)

I'd also like to add FIX-3.5.0: MNG-2199 It was working in Maven 3.2.2 but got broken the next release. This went unnoticed because the ITs were not correct. Back then I did not notice that Maven does not fail the build if it cannot resolve a parent but just logs a warning. The ITs did not check

Re: [DISCUSS] Big Scrub for proposed 3.5.0 (if we reset master)

Am 01/01/17 um 01:55 schrieb Michael Osipov: > Undecided: > MNG-5708: fixed by Christian's work Should not be done in that release. Let's ship all bugfixes affecting resolution together - not just one after the other. All or nothing. So nothing.

Re: [DISCUSS] Big Scrub for proposed 3.5.0 (if we reset master)

I would like to add MNG-6084 WONTFIX Support JSR 250 @PreDestory and @PostContruct On Sat, Dec 31, 2016 at 5:17 PM, Michael Osipov wrote: > Am 2017-01-01 um 02:11 schrieb Anton Tanasenko: > >> FIX-3.5.0: >> MNG- WONTFIX Add a ProjectArtifactsCache

Re: [DISCUSS] Big Scrub for proposed 3.5.0 (if we reset master)

Am 2017-01-01 um 02:11 schrieb Anton Tanasenko: FIX-3.5.0: MNG- WONTFIX Add a ProjectArtifactsCache similar to PluginArtifactsCache That's actually a https://issues.apache.org/jira/browse/MNG-6025 JIRA adjusted, thank you. Stephen, please update your list with MNG-6025.

Re: [DISCUSS] Big Scrub for proposed 3.5.0 (if we reset master)

FIX-3.5.0: MNG- WONTFIX Add a ProjectArtifactsCache similar to PluginArtifactsCache That's actually a https://issues.apache.org/jira/browse/MNG-6025 2017-01-01 2:55 GMT+02:00 Michael Osipov : > I just went through the list my issues. Here is a safe list I

Re: [DISCUSS] Big Scrub for proposed 3.5.0 (if we reset master)

I just went through the list my issues. Here is a safe list I would merge/cherry-pick into new master: FIX-3.5.0: MNG-5457, MNG-5567, MNG-5579, MNG-5607, MNG-5815, MNG-5954, MNG-5963, MNG-5975, MNG-5977, MNG-6001, MNG-6003, MNG-6029, MNG-6081, MNG-6102, MNG-6106, MNG-6115, MNG-6136, MNG-6137,

Re: [DISCUSS] Big Scrub for proposed 3.5.0 (if we reset master)

We need to figure out what is what. Also when making a proposal please reply to the original message not previous proposals On 31 December 2016 at 22:12, Guillaume Boué wrote: > > Le 31/12/2016 à 22:14, Stephen Connolly a écrit : > >> FIX-3.5.0: MNG-5607, MNG-5815, MNG-5823,

Re: [DISCUSS] Big Scrub for proposed 3.5.0 (if we reset master)

Here is the wiki page to track proposals https://cwiki.apache.org/confluence/display/MAVEN/Roadmap+2017 On 31 December 2016 at 21:34, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > Apache Proverb: If it doesn't happen on a mailing list then it is only a > rumour! > > I will keep

Re: [DISCUSS] Big Scrub for proposed 3.5.0 (if we reset master)

Le 31/12/2016 à 22:14, Stephen Connolly a écrit : FIX-3.5.0: MNG-5607, MNG-5815, MNG-5823, MNG-5824, MNG-5836, MNG-5837, MNG-5889, MNG-5904, MNG-5946, MNG-5963, MNG-5967, MNG-5968, MNG-6001, MNG-6003, MNG-6078 I think colourised logging probably should be 3.5.x but I am open to the idea of

Re: [DISCUSS] Big Scrub for proposed 3.5.0 (if we reset master)

Christian, to avoid confusion, could you reply to the original message if you are adding proposals... reply to proposals if you are seconding? On 31 December 2016 at 21:31, Christian Schulte wrote: > Am 31.12.2016 um 22:14 schrieb Stephen Connolly: > > FIX-3.5.0: MNG-5607,

Re: [DISCUSS] Big Scrub for proposed 3.5.0 (if we reset master)

Apache Proverb: If it doesn't happen on a mailing list then it is only a rumour! I will keep track and summarise on cwiki, but we need proposals and seconds on the ML -Stephen On Sat 31 Dec 2016 at 21:26, Michael Osipov wrote: > Am 2016-12-31 um 21:10 schrieb Stephen

Re: [DISCUSS] Big Scrub for proposed 3.5.0 (if we reset master)

Am 31.12.2016 um 22:14 schrieb Stephen Connolly: > FIX-3.5.0: MNG-5607, MNG-5815, MNG-5823, MNG-5824, MNG-5836, MNG-5837, > MNG-5889, MNG-5904, MNG-5946, MNG-5963, MNG-5967, MNG-5968, MNG-6001, > MNG-6003, MNG-6078 > > I think colourised logging probably should be 3.5.x but I am open to the >

Re: [DISCUSS] Big Scrub for proposed 3.5.0 (if we reset master)

Am 2016-12-31 um 21:10 schrieb Stephen Connolly: Here are the changes in current master since 3.3.9 (with some minor changes omitted) Issue ID Target Version Summary == MNG-1577 WONTFIX dependencyManagement

Re: [DISCUSS] Big Scrub for proposed 3.5.0 (if we reset master)

FIX-3.5.0: MNG-5607, MNG-5815, MNG-5823, MNG-5824, MNG-5836, MNG-5837, MNG-5889, MNG-5904, MNG-5946, MNG-5963, MNG-5967, MNG-5968, MNG-6001, MNG-6003, MNG-6078 I think colourised logging probably should be 3.5.x but I am open to the idea of making it 3.5.0 as it *should* not affect the build

[DISCUSS] Big Scrub for proposed 3.5.0 (if we reset master)

Here are the changes in current master since 3.3.9 (with some minor changes omitted) Issue ID Target Version Summary == MNG-1577 WONTFIX dependencyManagement does not work for