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

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

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

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

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

[GitHub] maven issue #115: Change out JAVA_HOME. Add JRE used. JRE used print /jre an...

Github user michael-o commented on the issue: https://github.com/apache/maven/pull/115 The diff is huge, you have a line ending issue. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this

[GitHub] maven pull request #115: Change out JAVA_HOME. Add JRE used. JRE used print ...

GitHub user marcelosv opened a pull request: https://github.com/apache/maven/pull/115 Change out JAVA_HOME. Add JRE used. JRE used print /jre and JAVA_HOME… I read the discursion of issue MNG-5756 and I change code out for JAVA_HOME and JRE. Now, print two information to

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

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

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

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: Updates to Java9 Compatibility Page

I have reopened the issue and added the plugin to Confluence table. On Fri, May 12, 2017 at 3:13 PM, Enrico Olivelli wrote: > Hi, > I think that all the issues related to the maven-war-plugin can be set > to "done", as apparently the maven-war-plugin is no more affected by

Updates to Java9 Compatibility Page

Hi, I think that all the issues related to the maven-war-plugin can be set to "done", as apparently the maven-war-plugin is no more affected by the xstream Java9 issue. https://cwiki.apache.org/confluence/display/MAVEN/Java+9+-+Jigsaw Maybe it would be good to report current Surefire problems

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

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: Re: [MNG-5567] Zip files are not included in classpaths at all

Done. > Gesendet: Freitag, 12. Mai 2017 um 12:47 Uhr > Von: "Robert Scholte" > An: "Maven Developers List" > Betreff: Re: [MNG-5567] Zip files are not included in classpaths at all > > I would like to move this to the next major version of Maven. >

Re: [MNG-5567] Zip files are not included in classpaths at all

I would like to move this to the next major version of Maven. Now it is the (package-)type of the dependency which decides if it should be on the classpath or not. I don't think that's correct, it should either be the compiler-plugin or the specific packaging plugin. (Maven itself should not

Maven-monitor still in use?

I''m looking to make a build radiator. Something like this - https://www.stevefenton.co.uk/wp-content/uploads/2015/07/cruiser.jpg I don't want to scrape logs to detect maven phase changes, and corresponding pass/fail, I want to use a plugin. I think that plugin is Maven-monitor Online

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

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: Timeline for maven-site-plugin 3.7?

Hi, There is no formal timeline, but if there is interest from community to work toward a release, let's go. The first release that has to be done is Doxia 1.8 [1]: as you can see, there is one issue that is not fixed yet. And I suppose we should have a review of recent DOXIA Jira issues to