Re: [MNG-6169] Lifecycle/binding plugin version updates

2017-07-02 Thread Michael Osipov
Am 2017-05-11 um 22:30 schrieb Michael Osipov: Who seconds MNG-6169 for 3.5.1? I have a fully working branch (MNG-6169_2/not-updated-MJAR-MCOMPILER) passing all ITs on Windows 10 and FreeBSD 10.3-RELEASE. Jenkins build is flaky with notorious file://target/null artifact not found. Some

Re: [MNG-6169] Lifecycle/binding plugin version updates

2017-05-16 Thread Hervé BOUTEMY
Le mardi 16 mai 2017, 22:20:35 CEST Stephen Connolly a écrit : > On Tue 16 May 2017 at 22:40, Hervé BOUTEMY wrote: > > Le lundi 15 mai 2017, 07:20:08 CEST Stephen Connolly a écrit : > > > On Sun 14 May 2017 at 08:51, Hervé BOUTEMY > > > > wrote: > >

Re: [MNG-6169] Lifecycle/binding plugin version updates

2017-05-16 Thread Stephen Connolly
On Tue 16 May 2017 at 22:40, Hervé BOUTEMY wrote: > Le lundi 15 mai 2017, 07:20:08 CEST Stephen Connolly a écrit : > > On Sun 14 May 2017 at 08:51, Hervé BOUTEMY > wrote: > > > thank you Robert: this is exactly the logic I was looking for, and > > >

Re: [MNG-6169] Lifecycle/binding plugin version updates

2017-05-16 Thread Hervé BOUTEMY
Le lundi 15 mai 2017, 07:20:08 CEST Stephen Connolly a écrit : > On Sun 14 May 2017 at 08:51, Hervé BOUTEMY wrote: > > thank you Robert: this is exactly the logic I was looking for, and > > explanation > > of changes over time to improve user experience through

Re: [MNG-6169] Lifecycle/binding plugin version updates

2017-05-15 Thread Michael Osipov
Am 2017-05-15 um 09:20 schrieb Stephen Connolly: On Sun 14 May 2017 at 08:51, Hervé BOUTEMY wrote: thank you Robert: this is exactly the logic I was looking for, and explanation of changes over time to improve user experience through reproducibility. Now the question

Re: [MNG-6169] Lifecycle/binding plugin version updates

2017-05-15 Thread Stephen Connolly
On Sun 14 May 2017 at 08:51, Hervé BOUTEMY wrote: > thank you Robert: this is exactly the logic I was looking for, and > explanation > of changes over time to improve user experience through reproducibility. > > Now the question is: should we change default plugin versions

Re: [MNG-6169] Lifecycle/binding plugin version updates

2017-05-14 Thread Michael Osipov
Am 2017-05-14 um 09:33 schrieb Hervé BOUTEMY: I don't understand what changed in Maven 3.1.0-alpha-1 that changed the behaviour: did you find which issue was fixed? Unfortunately not. Issue titles weren't helpful, commit messages also. I assume this is an Aether update. Adding a pointer to

Re: [MNG-6169] Lifecycle/binding plugin version updates

2017-05-14 Thread Hervé BOUTEMY
thank you Robert: this is exactly the logic I was looking for, and explanation of changes over time to improve user experience through reproducibility. Now the question is: should we change default plugin versions in Maven core? Does it improve Maven or not? To me, changing default plugin

Re: [MNG-6169] Lifecycle/binding plugin version updates

2017-05-14 Thread Hervé BOUTEMY
I don't understand what changed in Maven 3.1.0-alpha-1 that changed the behaviour: did you find which issue was fixed? Adding a pointer to that issue as comment (and not only in git commit message) would be useful before merging so that this change is understood when reading the code thanks

Re: [MNG-6169] Lifecycle/binding plugin version updates

2017-05-13 Thread Michael Osipov
Am 2017-05-13 um 23:39 schrieb Michael Osipov: Am 2017-05-13 um 22:38 schrieb Hervé BOUTEMY: Le samedi 13 mai 2017, 00:58:45 CEST Michael Osipov a écrit : Am 2017-05-13 um 00:30 schrieb Hervé BOUTEMY: Le vendredi 12 mai 2017, 13:50:37 CEST Michael Osipov a écrit : Am 2017-05-12 um 08:25

Re: [MNG-6169] Lifecycle/binding plugin version updates

2017-05-13 Thread Michael Osipov
Am 2017-05-13 um 22:38 schrieb Hervé BOUTEMY: Le samedi 13 mai 2017, 00:58:45 CEST Michael Osipov a écrit : Am 2017-05-13 um 00:30 schrieb Hervé BOUTEMY: Le vendredi 12 mai 2017, 13:50:37 CEST Michael Osipov a écrit : Am 2017-05-12 um 08:25 schrieb Hervé BOUTEMY: Jenkins build is not flaky:

Re: [MNG-6169] Lifecycle/binding plugin version updates

2017-05-13 Thread Robert Scholte
On Sat, 13 May 2017 22:38:55 +0200, Hervé BOUTEMY wrote: Le samedi 13 mai 2017, 00:58:45 CEST Michael Osipov a écrit : Am 2017-05-13 um 00:30 schrieb Hervé BOUTEMY: > Le vendredi 12 mai 2017, 13:50:37 CEST Michael Osipov a écrit : >> Am 2017-05-12 um 08:25 schrieb

Re: [MNG-6169] Lifecycle/binding plugin version updates

2017-05-13 Thread Hervé BOUTEMY
Le samedi 13 mai 2017, 00:58:45 CEST Michael Osipov a écrit : > Am 2017-05-13 um 00:30 schrieb Hervé BOUTEMY: > > Le vendredi 12 mai 2017, 13:50:37 CEST Michael Osipov a écrit : > >> Am 2017-05-12 um 08:25 schrieb Hervé BOUTEMY: > >>> Jenkins build is not flaky: it is strict on dependency

Re: [MNG-6169] Lifecycle/binding plugin version updates

2017-05-13 Thread Martin Gainty
egration-testing/commit/5c01864e44c7c96cac95545e8568acd044b6d7dc [https://avatars3.githubusercontent.com/u/573017?v=3=200]<https://github.com/apache/maven-integration-testing/commit/5c01864e44c7c96cac95545e8568acd044b6d7dc> [MNG-6169] Lifecycle/binding plugin version updates · apache/maven-i

Re: [MNG-6169] Lifecycle/binding plugin version updates

2017-05-12 Thread Michael Osipov
Am 2017-05-13 um 00:30 schrieb Hervé BOUTEMY: Le vendredi 12 mai 2017, 13:50:37 CEST Michael Osipov a écrit : Am 2017-05-12 um 08:25 schrieb Hervé BOUTEMY: Jenkins build is not flaky: it is strict on dependency resolution from cache, which is an intent, not a bug This pretty much explains

Re: [MNG-6169] Lifecycle/binding plugin version updates

2017-05-12 Thread Hervé BOUTEMY
Le vendredi 12 mai 2017, 13:50:37 CEST Michael Osipov a écrit : > Am 2017-05-12 um 08:25 schrieb Hervé BOUTEMY: > > Jenkins build is not flaky: it is strict on dependency resolution from > > cache, which is an intent, not a bug > > This pretty much explains why a lot of ITs fail here at work with

Re: [MNG-6169] Lifecycle/binding plugin version updates

2017-05-12 Thread Michael Osipov
Am 2017-05-12 um 08:25 schrieb Hervé BOUTEMY: Jenkins build is not flaky: it is strict on dependency resolution from cache, which is an intent, not a bug Traced down last missing dependencies and added them to Bootstrap IT. Branch MNG-6169 created on the Core ITs. Michael

Re: [MNG-6169] Lifecycle/binding plugin version updates

2017-05-12 Thread Michael Osipov
Am 2017-05-11 um 22:46 schrieb Robert Scholte: Is m-compiler-p on 3.6.1? please change to 3.5.1 until jigsaw stuff works correctly. Version has been downgraded. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For

Re: [MNG-6169] Lifecycle/binding plugin version updates

2017-05-12 Thread Chas Honton
Can we declare explicitly that this pom does not inherit from super pom? Chas > On May 12, 2017, at 4:50 AM, Michael Osipov wrote: > >> Am 2017-05-12 um 08:25 schrieb Hervé BOUTEMY: >> Jenkins build is not flaky: it is strict on dependency resolution from cache, >> which

Re: [MNG-6169] Lifecycle/binding plugin version updates

2017-05-12 Thread Michael Osipov
Am 2017-05-12 um 19:23 schrieb Chas Honton: How can the super pom be explicitly added to the project's pom? Not necessary, the Super POM is in a JAR distributed with Maven and automatically used. On May 12, 2017, at 4:50 AM, Michael Osipov wrote: Am 2017-05-12 um

Re: [MNG-6169] Lifecycle/binding plugin version updates

2017-05-12 Thread Chas Honton
How can the super pom be explicitly added to the project's pom? Chas > On May 12, 2017, at 4:50 AM, Michael Osipov wrote: > >> Am 2017-05-12 um 08:25 schrieb Hervé BOUTEMY: >> Jenkins build is not flaky: it is strict on dependency resolution from cache, >> which is an

Re: [MNG-6169] Lifecycle/binding plugin version updates

2017-05-12 Thread Michael Osipov
Am 2017-05-12 um 08:25 schrieb Hervé BOUTEMY: Jenkins build is not flaky: it is strict on dependency resolution from cache, which is an intent, not a bug This pretty much explains why a lot of ITs fail here at work with a empty repo. I will to work this through. that's why I don't like

Re: [MNG-6169] Lifecycle/binding plugin version updates

2017-05-12 Thread Hervé BOUTEMY
Jenkins build is not flaky: it is strict on dependency resolution from cache, which is an intent, not a bug that's why I don't like changing default plugins versions: 1. depending on default plugins versions is a bad practice: IMHO, having old plugins helps people know that they should not

Re: [MNG-6169] Lifecycle/binding plugin version updates

2017-05-11 Thread Michael Osipov
:11-05-2017 22:30 (GMT+01:00) Aan: Maven Developers List <dev@maven.apache.org> Onderwerp: [MNG-6169] Lifecycle/binding plugin version updates Who seconds MNG-6169 for 3.5.1? I have a fully working branch (MNG-6169_2/not-updated-MJAR-MCOMPILER) passing all ITs on Windows 10 and FreeBSD

Re: [MNG-6169] Lifecycle/binding plugin version updates

2017-05-11 Thread Robert Scholte
pache.org> Onderwerp: [MNG-6169] Lifecycle/binding plugin version updates Who seconds MNG-6169 for 3.5.1? I have a fully working branch (MNG-6169_2/not-updated-MJAR-MCOMPILER) passing all ITs on Windows 10 and FreeBSD 10.3-RELEASE. Jenkins build is flaky with notorious file://target/null artifa

[MNG-6169] Lifecycle/binding plugin version updates

2017-05-11 Thread Michael Osipov
Who seconds MNG-6169 for 3.5.1? I have a fully working branch (MNG-6169_2/not-updated-MJAR-MCOMPILER) passing all ITs on Windows 10 and FreeBSD 10.3-RELEASE. Jenkins build is flaky with notorious file://target/null artifact not found. Some bindings haven't been updated because they cause