Re: maven-site-plugin: Generating (X)HTML5 instead of XHTML - how?

On 15 Apr 2018, at 1:29 AM, Hervé BOUTEMY wrote: > yes, this will require a xhtml5 Doxia sink > > since each skin defines a site template as direct html source (without Doxia > interaction), the maven-site-plugin switch from xhtml to xhtml5 would have to > be done on

Re: Second MNG-6386

Am 2018-05-01 um 19:40 schrieb Robert Scholte: Hi Michael, to me it looks like the tests don't proof there's an issue. I only see that testDir.toURI() being replaced with testDir.toPath().toUri() while the actual value stays the same. No, it doesn't on Windows. File#toURI() is broken.

Re: Disable maven-checkstyle-plugin ?

I added: true ...to the pom.xml file, at the top level, above dependencies, and below description. I then re-ran `git push Heroku master`, but got the same error. What am I missing? On 5/1/18, 11:12 AM, "Karl Heinz Marbaise" wrote: Hi,

Re: Disable maven-checkstyle-plugin ?

Hi, On 01/05/18 19:55, Vik Rubenfeld wrote: I’m getting the following error during build on Heroku: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-checkstyle-plugin:2.16:check (verify) on project server-async: Failed during checkstyle execution: Unable to find suppressions

Re: Preparing next m-pmd-p release

Hi Andreas, On 01/05/18 19:55, Andreas Dangel wrote: Hi Karl Heinz, I can do it. Then, the build should be good again :) It should...and just go on... Kind regards Karl Heinz Marbaise Regards, Andreas Am 01.05.2018 um 19:50 schrieb Karl Heinz Marbaise: Hi Andreas, based on having

Disable maven-checkstyle-plugin ?

I’m getting the following error during build on Heroku: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-checkstyle-plugin:2.16:check (verify) on project server-async: Failed during checkstyle execution: Unable to find suppressions file at location:

Re: Preparing next m-pmd-p release

Hi Karl Heinz, I can do it. Then, the build should be good again :) Regards, Andreas Am 01.05.2018 um 19:50 schrieb Karl Heinz Marbaise: > Hi Andreas, > > based on having integrated the branches MPMD-252 and MNGSITE-332 into > master you can also remove the appropriate branches... > > Should

Re: Preparing next m-pmd-p release

Hi Andreas, based on having integrated the branches MPMD-252 and MNGSITE-332 into master you can also remove the appropriate branches... Should I integrate the branch MPMD-262 into master ? Or you would you prefer to do it ? Kind regards Karl Heinz Marbaise On 01/05/18 17:50, Andreas

Re: Second MNG-6386

Hi Michael, to me it looks like the tests don't proof there's an issue. I only see that testDir.toURI() being replaced with testDir.toPath().toUri() while the actual value stays the same. I would expect at least one new test that fails now, but will succeed with the change. thanks, Robert

Re: Preparing next m-pmd-p release

Hi Andreas, just fine go ahead... Kind regards Karl Heinz Marbaise On 01/05/18 19:32, Karl Heinz Marbaise wrote: Hi Andreas, On 01/05/18 17:50, Andreas Dangel wrote: Hi, I'm preparing a new release of m-pmd-p. I've seen two issues, which already have branches ready. Are there any reasons,

Re: Preparing next m-pmd-p release

Hi Andreas, On 01/05/18 17:50, Andreas Dangel wrote: Hi, I'm preparing a new release of m-pmd-p. I've seen two issues, which already have branches ready. Are there any reasons, they should not be included? If not, I'm going to merge/pick them. * Upgrade parent to 31 [MPMD-252] * Change

Re: Preparing next m-pmd-p release

Am 2018-05-01 um 17:50 schrieb Andreas Dangel: Hi, I'm preparing a new release of m-pmd-p. I've seen two issues, which already have branches ready. Are there any reasons, they should not be included? If not, I'm going to merge/pick them. * Upgrade parent to 31 [MPMD-252] * Change download

Preparing next m-pmd-p release

Hi, I'm preparing a new release of m-pmd-p. I've seen two issues, which already have branches ready. Are there any reasons, they should not be included? If not, I'm going to merge/pick them. * Upgrade parent to 31 [MPMD-252] * Change download template to not use md5 anymore [MNGSITE-332]

ApacheCon North America 2018 schedule is now live.

Dear Apache Enthusiast, We are pleased to announce our schedule for ApacheCon North America 2018. ApacheCon will be held September 23-27 at the Montreal Marriott Chateau Champlain in Montreal, Canada. Registration is open! The early bird rate of $575 lasts until July 21, at which time it

Second MNG-6386

Folks, who seconds MNG-6386 for 3.5.4 which I have found during SCM-877. ${project.baseUri} is an invalid URL. NIO2 offers a solution for that. Michael - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional

[ANN] Apache Maven Resources Plugin Version 3.1.0 Released

The Apache Maven team is pleased to announce the release of the Apache Maven Resources Plugin Version 3.1.0. https://maven.apache.org/plugins/maven-resources-plugin/ The Resources Plugin handles the copying of project resources to the output directory. There are two different kinds of