Re: Maven Site vs Reporting Plugin workflows?

Hi, The change is explained here: http://maven.apache.org/plugins/maven-site-plugin/maven-3.html The injection is done in DefaultReportingConverter [1] At the beginning, the dream was to remove element from pom.xml: then we later found that we could not since this is the only place where

Re: Maven Resolver 1.1

it would be great if MNG-6183 description included a sample debug message before the change and after the change: I can't get what this change is about really And of course, I don't get the next step with Resolver API... Regards, Hervé Le mardi 14 mars 2017, 21:24:58 CET Christian Schulte a

Re: Release build failing with current master (was Re: [PING] The GIT master branch of Maven has unreleased changes that do not pass a release build)

Well I'm not feeling 100% atm with the flu, so probably be Monday before I have the energy for a release On Wed 15 Mar 2017 at 22:16, Christian Schulte wrote: > Am 03/15/17 um 23:00 schrieb Robert Scholte: > > The javadoc-fix is easy, but the result of >

Re: Distribution file permission issue with current master.

no issue for me on Linux I don't understand what happens to you: I suppose this is once again related to FreeBSD I can't do anything for you Regards, Hervé Le mardi 14 mars 2017, 22:29:28 CET Christian Schulte a écrit : > Hi, > > see the attachment. After unzipping the binary distribution, I

Re: Maven Resolver 1.1

Am 03/15/17 um 23:31 schrieb Hervé BOUTEMY: > it would be great if MNG-6183 description included a sample debug message > before the change and after the change: I can't get what this change is about > really Will update the issue. > And of course, I don't get the next step with Resolver

Re: Release build failing with current master (was Re: [PING] The GIT master branch of Maven has unreleased changes that do not pass a release build)

The javadoc-fix is easy, but the result of modello-maven-plugin:1.9.0:xdoc now causes issues because html4 is not the same as balanced xml. Need to think about how to fix this. Maybe this commit should be reverted. Robert On Wed, 15 Mar 2017 22:40:54 +0100, Christian Schulte

Re: Distribution file permission issue with current master.

Am 03/15/17 um 23:37 schrieb Hervé BOUTEMY: > no issue for me on Linux > I don't understand what happens to you: I suppose this is once again related > to FreeBSD > I can't do anything for you Thanks for taking a look. It's happening with the zip distribution only. It's not happening using the

Re: Maven Site vs Reporting Plugin workflows?

Hervé thanks for the pointer. The Default Reporting Converter looks like it reads and normalizes content from the pom's various formats to the maven model. I don't see anything in that class that would indicate it converting into `org.apache.maven.reporting.exec.ReportPlugin` and injecting that

Re: Release build failing with current master (was Re: [PING] The GIT master branch of Maven has unreleased changes that do not pass a release build)

ok, so that argument should be moved to a java8 activated profile. On Wed, 15 Mar 2017 22:27:11 +0100, Christian Schulte wrote: Am 03/15/17 um 21:50 schrieb Michael Osipov: Am 2017-03-15 um 21:39 schrieb Christian Schulte: Hi, this is a real issue. A release build using

Re: Release build failing with current master (was Re: [PING] The GIT master branch of Maven has unreleased changes that do not pass a release build)

Am 03/15/17 um 22:30 schrieb Robert Scholte: > ok, so that argument should be moved to a java8 activated profile. Can you do this, please? Regards, -- Christian - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For

Release build failing with current master (was Re: [PING] The GIT master branch of Maven has unreleased changes that do not pass a release build)

Hi, this is a real issue. A release build using JDK 7 with current master is not possible. See Exit code: 1 - javadoc: error - invalid flag: -Xdoclint:none Regards, --

Re: New Branch SUREFIRE-1342

Hi Guillaume Boué, Have you found a spare time to test the branch? Cheers Tibor On Mon, Mar 13, 2017 at 11:04 PM, Guillaume Boué wrote: > Hi, > > I finished setting up a FreeBSD VM with a couple of Maven and JDK > versions, so I'll be testing this extensively (on Ubuntu as

Re: Release build failing with current master (was Re: [PING] The GIT master branch of Maven has unreleased changes that do not pass a release build)

Am 03/15/17 um 21:50 schrieb Michael Osipov: > Am 2017-03-15 um 21:39 schrieb Christian Schulte: >> Hi, >> >> this is a real issue. A release build using JDK 7 with current master is >> not possible. See >> >>

Re: Release build failing with current master (was Re: [PING] The GIT master branch of Maven has unreleased changes that do not pass a release build)

Am 2017-03-15 um 21:39 schrieb Christian Schulte: Hi, this is a real issue. A release build using JDK 7 with current master is not possible. See Exit code: 1 - javadoc:

Re: [DISCUSS] Retrospective on Maven 3.5.0-alpha-1

--first-parent On Wed 15 Mar 2017 at 00:39, Christian Schulte wrote: > Am 03/14/17 um 01:27 schrieb Jeff Jensen: > >> The date of the commit is not the date it got committed to master, but > the > > date it got committed to some branch, no longer existing after the > commit. >

Re: Release build failing with current master (was Re: [PING] The GIT master branch of Maven has unreleased changes that do not pass a release build)

Am 03/15/17 um 23:00 schrieb Robert Scholte: > The javadoc-fix is easy, but the result of modello-maven-plugin:1.9.0:xdoc > now causes issues because html4 is not the same as balanced xml. Need to > think about how to fix this. > Maybe this commit should be reverted. Cannot tell. Stephen? Can