[jira] [Created] (MCHECKSTYLE-337) checkstyle:check only supports xml output format, but the docs say it supports plain as well

2017-05-23 Thread JIRA
Stig Rohde Døssing created MCHECKSTYLE-337: -- Summary: checkstyle:check only supports xml output format, but the docs say it supports plain as well Key: MCHECKSTYLE-337 URL: https://issues.apache.org/jira

[jira] [Commented] (MNG-6223) mvn -f outputs invalid error when specifying POM directory

2017-05-24 Thread JIRA
[ https://issues.apache.org/jira/browse/MNG-6223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16023646#comment-16023646 ] Hervé Boutemy commented on MNG-6223: thank you for the reference: now we did a cor

[jira] [Created] (ARCHETYPE-528) Archetype:generate from repos besides central does not work

2017-05-25 Thread JIRA
João Cabrita created ARCHETYPE-528: -- Summary: Archetype:generate from repos besides central does not work Key: ARCHETYPE-528 URL: https://issues.apache.org/jira/browse/ARCHETYPE-528 Project: Maven

[jira] [Updated] (ARCHETYPE-528) Archetype:generate from repos besides central does not work

2017-05-25 Thread JIRA
[ https://issues.apache.org/jira/browse/ARCHETYPE-528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] João Cabrita updated ARCHETYPE-528: --- Description: {noformat} mvn -X -P camunda -DarchetypeCatalog=remote

[jira] [Commented] (ARCHETYPE-528) Archetype:generate from repos besides central does not work

2017-05-25 Thread JIRA
[ https://issues.apache.org/jira/browse/ARCHETYPE-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16024453#comment-16024453 ] João Cabrita commented on ARCHETYPE-528: Using the (undocume

[jira] [Commented] (ARCHETYPE-528) Archetype:generate from repos besides central does not work

2017-05-26 Thread JIRA
[ https://issues.apache.org/jira/browse/ARCHETYPE-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16026036#comment-16026036 ] João Cabrita commented on ARCHETYPE-528: And, after some more investiga

[jira] [Comment Edited] (ARCHETYPE-528) Archetype:generate from repos besides central does not work

2017-05-26 Thread JIRA
[ https://issues.apache.org/jira/browse/ARCHETYPE-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16026036#comment-16026036 ] João Cabrita edited comment on ARCHETYPE-528 at 5/26/17 9:1

[jira] [Created] (MRESOLVER-26) add Automatic-Module-Name entry to MANIFEST.MF for Java 9 automatic module names

2017-05-27 Thread JIRA
Hervé Boutemy created MRESOLVER-26: -- Summary: add Automatic-Module-Name entry to MANIFEST.MF for Java 9 automatic module names Key: MRESOLVER-26 URL: https://issues.apache.org/jira/browse/MRESOLVER-26

[jira] [Created] (MRESOLVER-27) turn artifacts into Java 9 modules

2017-05-27 Thread JIRA
Hervé Boutemy created MRESOLVER-27: -- Summary: turn artifacts into Java 9 modules Key: MRESOLVER-27 URL: https://issues.apache.org/jira/browse/MRESOLVER-27 Project: Maven Resolver Issue Type

[jira] [Updated] (MRESOLVER-26) add Automatic-Module-Name entry to MANIFEST.MF for Java 9 automatic module names

2017-05-27 Thread JIRA
[ https://issues.apache.org/jira/browse/MRESOLVER-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated MRESOLVER-26: --- Description: as discussed in dev ML: https://lists.apache.org/thread.html

[jira] [Updated] (MRESOLVER-26) add Automatic-Module-Name entry to MANIFEST.MF for Java 9 automatic module names

2017-05-27 Thread JIRA
[ https://issues.apache.org/jira/browse/MRESOLVER-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated MRESOLVER-26: --- Description: as discussed in dev ML: https://lists.apache.org/thread.html

[jira] [Updated] (MRESOLVER-27) turn artifacts into Java 9 modules

2017-05-27 Thread JIRA
[ https://issues.apache.org/jira/browse/MRESOLVER-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated MRESOLVER-27: --- Description: Java 9 is coming, and Maven Artifact Resolver: # has a chance to be turned

[jira] [Updated] (MRESOLVER-27) turn artifacts into Java 9 modules

2017-05-27 Thread JIRA
[ https://issues.apache.org/jira/browse/MRESOLVER-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated MRESOLVER-27: --- Affects Version/s: (was: Maven Artifact Resolver 1.0.3) Maven

[jira] [Updated] (MRESOLVER-26) add Automatic-Module-Name entry to MANIFEST.MF for Java 9 automatic module names

2017-05-27 Thread JIRA
[ https://issues.apache.org/jira/browse/MRESOLVER-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated MRESOLVER-26: --- Description: as discussed in dev ML: https://lists.apache.org/thread.html

[jira] [Commented] (MRESOLVER-26) add Automatic-Module-Name entry to MANIFEST.MF for Java 9 automatic module names

2017-05-27 Thread JIRA
[ https://issues.apache.org/jira/browse/MRESOLVER-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16027454#comment-16027454 ] Hervé Boutemy commented on MRESOLVER-26: proposed patch: http://git

[jira] [Updated] (MRESOLVER-27) turn artifacts into Java 9 modules

2017-05-27 Thread JIRA
[ https://issues.apache.org/jira/browse/MRESOLVER-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated MRESOLVER-27: --- Description: Java 9 with Jigsaw modules is coming Maven Artifact Resolver: # has a chance

[jira] [Commented] (MCHECKSTYLE-338) Add support for 'omitIgnoredModules'

2017-05-27 Thread JIRA
[ https://issues.apache.org/jira/browse/MCHECKSTYLE-338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16027573#comment-16027573 ] Guillaume Boué commented on MCHECKSTYLE-338: Fixed in [r1796441|

[jira] [Commented] (MCHECKSTYLE-337) checkstyle:check only supports xml output format, but the docs say it supports plain as well

2017-05-27 Thread JIRA
[ https://issues.apache.org/jira/browse/MCHECKSTYLE-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16027579#comment-16027579 ] Guillaume Boué commented on MCHECKSTYLE-337: I'm not sure why

[jira] [Closed] (MCHECKSTYLE-338) Add support for 'omitIgnoredModules'

2017-05-27 Thread JIRA
[ https://issues.apache.org/jira/browse/MCHECKSTYLE-338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Boué closed MCHECKSTYLE-338. -- Resolution: Fixed Assignee: Guillaume Boué Fix Version/s: 3.0.0

[jira] [Commented] (MCHECKSTYLE-337) checkstyle:check only supports xml output format, but the docs say it supports plain as well

2017-05-28 Thread JIRA
[ https://issues.apache.org/jira/browse/MCHECKSTYLE-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16027736#comment-16027736 ] Stig Rohde Døssing commented on MCHECKSTYLE-337: The first op

[jira] [Updated] (MNG-6164) Collections inconsistently immutable

2017-05-28 Thread JIRA
[ https://issues.apache.org/jira/browse/MNG-6164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated MNG-6164: --- Description: There are plenty of places where empty collections are returned from public API in

[jira] [Updated] (MNG-6164) Collections inconsistently immutable

2017-05-28 Thread JIRA
[ https://issues.apache.org/jira/browse/MNG-6164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated MNG-6164: --- Issue Type: Improvement (was: Bug) > Collections inconsistently immuta

[jira] [Updated] (MNG-6164) Collections inconsistently immutable

2017-05-28 Thread JIRA
[ https://issues.apache.org/jira/browse/MNG-6164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated MNG-6164: --- Priority: Minor (was: Critical) > Collections inconsistently immuta

[jira] [Closed] (MRESOLVER-26) add Automatic-Module-Name entry to MANIFEST.MF for Java 9 automatic module names

2017-05-28 Thread JIRA
[ https://issues.apache.org/jira/browse/MRESOLVER-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy closed MRESOLVER-26. -- Resolution: Fixed Assignee: Hervé Boutemy > add Automatic-Module-Name entry

[jira] [Created] (SUREFIRE-1375) Fixing build on Windows cmd.exe

2017-05-28 Thread JIRA
Guillaume Boué created SUREFIRE-1375: Summary: Fixing build on Windows cmd.exe Key: SUREFIRE-1375 URL: https://issues.apache.org/jira/browse/SUREFIRE-1375 Project: Maven Surefire Issue

[jira] [Updated] (SUREFIRE-1375) Fixing build on Windows cmd.exe

2017-05-28 Thread JIRA
[ https://issues.apache.org/jira/browse/SUREFIRE-1375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Boué updated SUREFIRE-1375: - Description: The Failsafe Plugin uses {{cxf-xjc-plugin}}, and the XJC tool, to

[jira] [Created] (SUREFIRE-1376) "The forked VM terminated without properly saying goodbye" when running Surefire in a very deep project structure on Windows

2017-05-28 Thread JIRA
URL: https://issues.apache.org/jira/browse/SUREFIRE-1376 Project: Maven Surefire Issue Type: Bug Components: Maven Failsafe Plugin, Maven Surefire Plugin Affects Versions: 2.20 Environment: Windows Reporter: Guillaume Boué When Surefire is ran on

[jira] [Updated] (SUREFIRE-1376) "The forked VM terminated without properly saying goodbye" when running Surefire in a very deep project structure on Windows

2017-05-28 Thread JIRA
[ https://issues.apache.org/jira/browse/SUREFIRE-1376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Boué updated SUREFIRE-1376: - Attachment: SUREFIRE-1376-prefix.patch > "The forked VM terminated without

[jira] [Comment Edited] (MSITE-793) MavenMultiPage example

2017-05-28 Thread JIRA
[ https://issues.apache.org/jira/browse/MSITE-793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1630#comment-1630 ] Hervé Boutemy edited comment on MSITE-793 at 5/28/17 9:1

[jira] [Updated] (MSITE-787) display what reports are added automatically when no reportSet is defined

2017-05-28 Thread JIRA
[ https://issues.apache.org/jira/browse/MSITE-787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated MSITE-787: Description: when no reportSet is defined, every report is added automatically: this is somewhat

[jira] [Commented] (MANTRUN-181) AttachArtifact task does not work in external Ant build file

2017-05-29 Thread JIRA
[ https://issues.apache.org/jira/browse/MANTRUN-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16028562#comment-16028562 ] Guillaume Boué commented on MANTRUN-181: Fixed in [r1796671|

[jira] [Commented] (SUREFIRE-1376) "The forked VM terminated without properly saying goodbye" when running Surefire in a very deep project structure on Windows

2017-05-29 Thread JIRA
[ https://issues.apache.org/jira/browse/SUREFIRE-1376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16028642#comment-16028642 ] Guillaume Boué commented on SUREFIRE-1376: -- It's {{260 - 12 - 1}

[jira] [Commented] (MANTRUN-181) AttachArtifact task does not work in external Ant build file

2017-05-29 Thread JIRA
[ https://issues.apache.org/jira/browse/MANTRUN-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16028656#comment-16028656 ] Guillaume Boué commented on MANTRUN-181: Follow-up in [r1796719|

[jira] [Created] (MNG-6238) maven deploy-file do not evalute ci friendly names from pom.xml

2017-05-30 Thread JIRA
Mariusz Smykuła created MNG-6238: Summary: maven deploy-file do not evalute ci friendly names from pom.xml Key: MNG-6238 URL: https://issues.apache.org/jira/browse/MNG-6238 Project: Maven

[jira] [Commented] (MNG-6238) maven deploy-file do not evalute ci friendly names from pom.xml

2017-05-30 Thread JIRA
[ https://issues.apache.org/jira/browse/MNG-6238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16029309#comment-16029309 ] Mariusz Smykuła commented on MNG-6238: -- Additionally, upload pom.xml is inv

[jira] [Created] (MDEPLOY-223) maven deploy-file do not evaluate ci friendly variables from pom.xml

2017-05-30 Thread JIRA
Mariusz Smykuła created MDEPLOY-223: --- Summary: maven deploy-file do not evaluate ci friendly variables from pom.xml Key: MDEPLOY-223 URL: https://issues.apache.org/jira/browse/MDEPLOY-223 Project

[jira] [Updated] (MDEPLOY-223) maven deploy-file do not evaluate ci friendly variables from pom.xml

2017-05-30 Thread JIRA
[ https://issues.apache.org/jira/browse/MDEPLOY-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mariusz Smykuła updated MDEPLOY-223: Description: Sample command: {code} ./mvnw deploy:deploy-file -Drevision=100 -Durl=file

[jira] [Commented] (MDEPLOY-150) deploy-file does not use repository in the same way as deploy

2017-05-30 Thread JIRA
[ https://issues.apache.org/jira/browse/MDEPLOY-150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16029351#comment-16029351 ] Mariusz Smykuła commented on MDEPLOY-150: - One reason for not using {{{de

[jira] [Comment Edited] (MDEPLOY-150) deploy-file does not use repository in the same way as deploy

2017-05-30 Thread JIRA
[ https://issues.apache.org/jira/browse/MDEPLOY-150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16029351#comment-16029351 ] Mariusz Smykuła edited comment on MDEPLOY-150 at 5/30/17 12:2

[jira] [Comment Edited] (MDEPLOY-150) deploy-file does not use repository in the same way as deploy

2017-05-30 Thread JIRA
[ https://issues.apache.org/jira/browse/MDEPLOY-150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16029351#comment-16029351 ] Mariusz Smykuła edited comment on MDEPLOY-150 at 5/30/17 12:2

[jira] [Commented] (MDEPLOY-223) maven deploy-file do not evaluate ci friendly variables from pom.xml

2017-05-30 Thread JIRA
[ https://issues.apache.org/jira/browse/MDEPLOY-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16029860#comment-16029860 ] Mariusz Smykuła commented on MDEPLOY-223: - workaround: {code} ./

[jira] [Created] (MANTRUN-201) Migrate plugin to Maven 3.0

2017-05-30 Thread JIRA
Guillaume Boué created MANTRUN-201: -- Summary: Migrate plugin to Maven 3.0 Key: MANTRUN-201 URL: https://issues.apache.org/jira/browse/MANTRUN-201 Project: Maven Antrun Plugin Issue Type

[jira] [Commented] (MANTRUN-201) Migrate plugin to Maven 3.0

2017-05-30 Thread JIRA
[ https://issues.apache.org/jira/browse/MANTRUN-201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16030060#comment-16030060 ] Guillaume Boué commented on MANTRUN-201: Fixed in [r1796930|

[jira] [Updated] (MDEPLOY-223) maven deploy-file do not evaluate ci friendly variables from pom.xml

2017-05-30 Thread JIRA
[ https://issues.apache.org/jira/browse/MDEPLOY-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mariusz Smykuła updated MDEPLOY-223: Description: Sample command: {code} ./mvnw deploy:deploy-file -Drevision=100 -Durl=file

[jira] [Comment Edited] (MDEPLOY-223) maven deploy-file do not evaluate ci friendly variables from pom.xml

2017-05-30 Thread JIRA
[ https://issues.apache.org/jira/browse/MDEPLOY-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16029860#comment-16029860 ] Mariusz Smykuła edited comment on MDEPLOY-223 at 5/30/17 9:0

[jira] [Closed] (MDEPLOY-223) maven deploy-file do not evaluate ci friendly variables from pom.xml

2017-05-30 Thread JIRA
[ https://issues.apache.org/jira/browse/MDEPLOY-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mariusz Smykuła closed MDEPLOY-223. --- Resolution: Not A Problem > maven deploy-file do not evaluate ci friendly variables f

[jira] [Issue Comment Deleted] (MNG-6238) maven deploy-file do not evalute ci friendly names from pom.xml

2017-05-30 Thread JIRA
[ https://issues.apache.org/jira/browse/MNG-6238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mariusz Smykuła updated MNG-6238: - Comment: was deleted (was: Additionally, upload pom.xml is invalid: {code} http://maven.apache.org

[jira] [Updated] (MNG-6238) maven deploy-file do not evalute ci friendly names from pom.xml

2017-05-30 Thread JIRA
[ https://issues.apache.org/jira/browse/MNG-6238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mariusz Smykuła updated MNG-6238: - Description: Sample command: {code} ./mvnw deploy:deploy-file -Drevision=100 -Durl=http://foo

[jira] [Closed] (MNG-6238) maven deploy-file do not evalute ci friendly names from pom.xml

2017-05-30 Thread JIRA
[ https://issues.apache.org/jira/browse/MNG-6238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mariusz Smykuła closed MNG-6238. Resolution: Not A Problem > maven deploy-file do not evalute ci friendly names from pom.

[jira] [Created] (MANTRUN-202) Fail the build when deprecated parameters tasks, sourceRoot or testSourceRoot are used

2017-05-30 Thread JIRA
Guillaume Boué created MANTRUN-202: -- Summary: Fail the build when deprecated parameters tasks, sourceRoot or testSourceRoot are used Key: MANTRUN-202 URL: https://issues.apache.org/jira/browse/MANTRUN-202

[jira] [Commented] (MANTRUN-202) Fail the build when deprecated parameters tasks, sourceRoot or testSourceRoot are used

2017-05-30 Thread JIRA
[ https://issues.apache.org/jira/browse/MANTRUN-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16030176#comment-16030176 ] Guillaume Boué commented on MANTRUN-202: Fixed in [r1796945|

[jira] [Created] (MANTRUN-203) Upgrade to maven-plugins 30

2017-05-30 Thread JIRA
Guillaume Boué created MANTRUN-203: -- Summary: Upgrade to maven-plugins 30 Key: MANTRUN-203 URL: https://issues.apache.org/jira/browse/MANTRUN-203 Project: Maven Antrun Plugin Issue Type

[jira] [Commented] (MANTRUN-203) Upgrade to maven-plugins 30

2017-05-30 Thread JIRA
[ https://issues.apache.org/jira/browse/MANTRUN-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16030181#comment-16030181 ] Guillaume Boué commented on MANTRUN-203: Fixed in [r1796947|

[jira] [Commented] (MANTRUN-197) Can't use ant import task in target xml

2017-05-30 Thread JIRA
[ https://issues.apache.org/jira/browse/MANTRUN-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16030224#comment-16030224 ] Guillaume Boué commented on MANTRUN-197: This can be worked around easil

[jira] [Updated] (MANTRUN-197) Can't use ant import task in target xml

2017-05-30 Thread JIRA
[ https://issues.apache.org/jira/browse/MANTRUN-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Boué updated MANTRUN-197: --- Issue Type: Wish (was: Bug) > Can't use ant import task in ta

[jira] [Commented] (MANTRUN-172) Properties passed to Maven as -D don't get passed to invocations when a profile sets the same property

2017-05-31 Thread JIRA
[ https://issues.apache.org/jira/browse/MANTRUN-172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16032054#comment-16032054 ] Guillaume Boué commented on MANTRUN-172: This is actually unrelated to the

[jira] [Commented] (MCHECKSTYLE-337) checkstyle:check only supports xml output format, but the docs say it supports plain as well

2017-05-31 Thread JIRA
[ https://issues.apache.org/jira/browse/MCHECKSTYLE-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16032156#comment-16032156 ] Guillaume Boué commented on MCHECKSTYLE-337: Outputting a plain file

[jira] [Comment Edited] (MCHECKSTYLE-337) checkstyle:check only supports xml output format, but the docs say it supports plain as well

2017-05-31 Thread JIRA
[ https://issues.apache.org/jira/browse/MCHECKSTYLE-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16032156#comment-16032156 ] Guillaume Boué edited comment on MCHECKSTYLE-337 at 5/31/17 11:0

[jira] [Commented] (MDEP-420) The dependency:get goal does not download the associate pom, or provide an option to do that

2017-06-01 Thread JIRA
[ https://issues.apache.org/jira/browse/MDEP-420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1609#comment-1609 ] Guillaume Boué commented on MDEP-420: - I cannot reproduce this issue anymore

[jira] [Commented] (MDEP-569) copy fails on artifacts previously downloaded via get from repo specified via CLI

2017-06-01 Thread JIRA
[ https://issues.apache.org/jira/browse/MDEP-569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16033422#comment-16033422 ] Guillaume Boué commented on MDEP-569: - [{{dependency:get}}|https://maven.apache

[jira] [Commented] (MCHECKSTYLE-337) checkstyle:check only supports xml output format, but the docs say it supports plain as well

2017-06-01 Thread JIRA
[ https://issues.apache.org/jira/browse/MCHECKSTYLE-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16033529#comment-16033529 ] Stig Rohde Døssing commented on MCHECKSTYLE-337: I have a solu

[jira] [Updated] (MCHECKSTYLE-337) checkstyle:check only supports xml output format, but the docs say it supports plain as well

2017-06-01 Thread JIRA
[ https://issues.apache.org/jira/browse/MCHECKSTYLE-337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stig Rohde Døssing updated MCHECKSTYLE-337: --- Attachment: MCHECKSTYLE-337.patch Figured it out :) > checkstyle:ch

[jira] [Commented] (MSHADE-247) NullpointerException when createSourcesJar = true and source jar cannot be found

2017-06-01 Thread JIRA
[ https://issues.apache.org/jira/browse/MSHADE-247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16033661#comment-16033661 ] Guillaume Boué commented on MSHADE-247: --- Fixed in [r1797263|http://svn.apache

[jira] [Closed] (MDEP-420) The dependency:get goal does not download the associate pom, or provide an option to do that

2017-06-01 Thread JIRA
[ https://issues.apache.org/jira/browse/MDEP-420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Boué closed MDEP-420. --- Resolution: Fixed Fix Version/s: 3.0.1 > The dependency:get goal does not download the associ

[jira] [Closed] (MSHADE-247) NullpointerException when createSourcesJar = true and source jar cannot be found

2017-06-01 Thread JIRA
[ https://issues.apache.org/jira/browse/MSHADE-247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Boué closed MSHADE-247. - Resolution: Fixed Assignee: Guillaume Boué Fix Version/s: 3.0.1

[jira] [Commented] (MCHECKSTYLE-337) checkstyle:check only supports xml output format, but the docs say it supports plain as well

2017-06-03 Thread JIRA
[ https://issues.apache.org/jira/browse/MCHECKSTYLE-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16036068#comment-16036068 ] Guillaume Boué commented on MCHECKSTYLE-337: Thanks! The patch must

[jira] [Commented] (MDEP-560) maven-dependency-plugin ignores method references passed as parameter

2017-06-03 Thread JIRA
[ https://issues.apache.org/jira/browse/MDEP-560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16036074#comment-16036074 ] Guillaume Boué commented on MDEP-560: - This looks already fixed in version 3.0.1.

[jira] [Commented] (MDEP-569) copy fails on artifacts previously downloaded via get from repo specified via CLI

2017-06-03 Thread JIRA
[ https://issues.apache.org/jira/browse/MDEP-569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16036086#comment-16036086 ] Guillaume Boué commented on MDEP-569: - Yes, adding a {{remoteRepositories}} param

[jira] [Updated] (MCHECKSTYLE-337) checkstyle:check only supports xml output format, but the docs say it supports plain as well

2017-06-03 Thread JIRA
[ https://issues.apache.org/jira/browse/MCHECKSTYLE-337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stig Rohde Døssing updated MCHECKSTYLE-337: --- Attachment: MCHECKSTYLE-337.patch Whoops, first version was based off

[jira] [Commented] (MCHECKSTYLE-314) checkstyle:check should invoke the execution of this plugin's goal "checkstyle" prior to executing itself

2017-06-03 Thread JIRA
[ https://issues.apache.org/jira/browse/MCHECKSTYLE-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16036129#comment-16036129 ] Stig Rohde Døssing commented on MCHECKSTYLE-314: [~michael-o]

[jira] [Created] (MINVOKER-220) when description is too long, 2 spaces before status instead of 1

2017-06-04 Thread JIRA
Hervé Boutemy created MINVOKER-220: -- Summary: when description is too long, 2 spaces before status instead of 1 Key: MINVOKER-220 URL: https://issues.apache.org/jira/browse/MINVOKER-220 Project

[jira] [Closed] (MINVOKER-220) when description is too long, 2 spaces before status instead of 1

2017-06-04 Thread JIRA
[ https://issues.apache.org/jira/browse/MINVOKER-220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy closed MINVOKER-220. -- Resolution: Fixed > when description is too long, 2 spaces before status instead o

[jira] [Created] (MINVOKER-221) improve "run script" message with description of which script

2017-06-04 Thread JIRA
Hervé Boutemy created MINVOKER-221: -- Summary: improve "run script" message with description of which script Key: MINVOKER-221 URL: https://issues.apache.org/jira/browse/MINVOKER-221 Proj

[jira] [Updated] (MINVOKER-221) improve "run script" message with description of which script

2017-06-04 Thread JIRA
[ https://issues.apache.org/jira/browse/MINVOKER-221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated MINVOKER-221: --- Description: {noformat}[INFO] Building: projects/file-sets/dont-use-default-excludes

[jira] [Updated] (MINVOKER-221) improve "run script" message with description of which script

2017-06-04 Thread JIRA
[ https://issues.apache.org/jira/browse/MINVOKER-221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated MINVOKER-221: --- Description: {noformat}[INFO] Building: projects/file-sets/dont-use-default-excludes

[jira] [Created] (MSHARED-638) use script description instead of hardcoded "script" in messages

2017-06-04 Thread JIRA
Hervé Boutemy created MSHARED-638: - Summary: use script description instead of hardcoded "script" in messages Key: MSHARED-638 URL: https://issues.apache.org/jira/browse/MSHARED-638 Proj

[jira] [Updated] (MSHARED-638) use script description instead of hardcoded "script" in messages

2017-06-04 Thread JIRA
[ https://issues.apache.org/jira/browse/MSHARED-638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated MSHARED-638: -- Description: examples: {noformat}[DEBUG] no script found in directory: ... [DEBUG] no script

[jira] [Updated] (MSHARED-638) use script description instead of hardcoded "script" in messages

2017-06-04 Thread JIRA
[ https://issues.apache.org/jira/browse/MSHARED-638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated MSHARED-638: -- Description: examples: {noformat}[DEBUG] no script found in directory: ... [DEBUG] no script

[jira] [Commented] (MCHECKSTYLE-337) checkstyle:check only supports xml output format, but the docs say it supports plain as well

2017-06-04 Thread JIRA
[ https://issues.apache.org/jira/browse/MCHECKSTYLE-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16036299#comment-16036299 ] Guillaume Boué commented on MCHECKSTYLE-337: [~Srdo] It seems

[jira] [Updated] (MCHECKSTYLE-337) checkstyle:check only supports xml output format, but the docs say it supports plain as well

2017-06-04 Thread JIRA
[ https://issues.apache.org/jira/browse/MCHECKSTYLE-337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stig Rohde Døssing updated MCHECKSTYLE-337: --- Attachment: MCHECKSTYLE-337.patch That's what I get for not p

[jira] [Commented] (MCHECKSTYLE-337) checkstyle:check only supports xml output format, but the docs say it supports plain as well

2017-06-04 Thread JIRA
[ https://issues.apache.org/jira/browse/MCHECKSTYLE-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16036348#comment-16036348 ] Guillaume Boué commented on MCHECKSTYLE-337: Thanks for the p

[jira] [Closed] (MCHECKSTYLE-337) checkstyle:check only supports xml output format, but the docs say it supports plain as well

2017-06-04 Thread JIRA
[ https://issues.apache.org/jira/browse/MCHECKSTYLE-337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Boué closed MCHECKSTYLE-337. -- Resolution: Fixed Assignee: Guillaume Boué Fix Version/s: 3.0.0

[jira] [Closed] (MDEP-560) maven-dependency-plugin ignores method references passed as parameter

2017-06-04 Thread JIRA
[ https://issues.apache.org/jira/browse/MDEP-560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Boué closed MDEP-560. --- Resolution: Duplicate Fix Version/s: 3.0.1 > maven-dependency-plugin ignores method referen

[jira] [Comment Edited] (MDEP-560) maven-dependency-plugin ignores method references passed as parameter

2017-06-04 Thread JIRA
[ https://issues.apache.org/jira/browse/MDEP-560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16036074#comment-16036074 ] Guillaume Boué edited comment on MDEP-560 at 6/4/17 8:2

[jira] [Closed] (MSHARED-638) use script description instead of hardcoded "script" in messages

2017-06-04 Thread JIRA
[ https://issues.apache.org/jira/browse/MSHARED-638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy closed MSHARED-638. - Resolution: Fixed > use script description instead of hardcoded "script"

[jira] [Closed] (MINVOKER-221) improve "run script" message with description of which script

2017-06-04 Thread JIRA
[ https://issues.apache.org/jira/browse/MINVOKER-221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy closed MINVOKER-221. -- Resolution: Fixed Fix Version/s: 3.0.1 > improve "run script" message wit

[jira] [Commented] (MNG-6209) inconsistent activation of components from multiple extensions=true plugins

2017-06-05 Thread JIRA
[ https://issues.apache.org/jira/browse/MNG-6209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16037399#comment-16037399 ] Hervé Boutemy commented on MNG-6209: since when is this thread classloader use

[jira] [Commented] (MASSEMBLY-263) Include component location information

2017-06-05 Thread JIRA
[ https://issues.apache.org/jira/browse/MASSEMBLY-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16037406#comment-16037406 ] Hervé Boutemy commented on MASSEMBLY-263: - [r1002344|http://svn.apache

[jira] [Commented] (MASSEMBLY-331) assembly descriptor doesn't seem to property substitute properties

2017-06-05 Thread JIRA
[ https://issues.apache.org/jira/browse/MASSEMBLY-331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16037689#comment-16037689 ] Hervé Boutemy commented on MASSEMBLY-331: - [r694529|http://svn.apache

[jira] [Updated] (MASSEMBLY-331) assembly descriptor doesn't seem to property substitute properties

2017-06-05 Thread JIRA
[ https://issues.apache.org/jira/browse/MASSEMBLY-331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated MASSEMBLY-331: Description: For the following assembly.xml: {code:xml} tar.gz

[jira] [Commented] (MNG-6209) inconsistent activation of components from multiple extensions=true plugins

2017-06-05 Thread JIRA
[ https://issues.apache.org/jira/browse/MNG-6209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16037692#comment-16037692 ] Hervé Boutemy commented on MNG-6209: I looked into m-assembly-p history and found

[jira] [Commented] (MDEP-516) Go-offline does not find module dependencies in multi-module build.

2017-06-05 Thread JIRA
[ https://issues.apache.org/jira/browse/MDEP-516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16038036#comment-16038036 ] Hervé commented on MDEP-516: Any update on this? MDEP-516 and MDEP-204 are still open wit

[jira] [Commented] (MDEPLOY-221) deploy generates wrong timestamps in maven-metadata.xml

2017-06-06 Thread JIRA
[ https://issues.apache.org/jira/browse/MDEPLOY-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16039531#comment-16039531 ] Guillaume Boué commented on MDEPLOY-221: Can someone try using the latest 3

[jira] [Closed] (MANTRUN-202) Fail the build when deprecated parameters tasks, sourceRoot or testSourceRoot are used

2017-06-06 Thread JIRA
[ https://issues.apache.org/jira/browse/MANTRUN-202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Boué closed MANTRUN-202. -- Resolution: Fixed Fix Version/s: 3.0.0 > Fail the build when deprecated paramet

[jira] [Closed] (MANTRUN-201) Migrate plugin to Maven 3.0

2017-06-06 Thread JIRA
[ https://issues.apache.org/jira/browse/MANTRUN-201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Boué closed MANTRUN-201. -- Resolution: Fixed Fix Version/s: 3.0.0 > Migrate plugin to Maven

[jira] [Closed] (MANTRUN-181) AttachArtifact task does not work in external Ant build file

2017-06-06 Thread JIRA
[ https://issues.apache.org/jira/browse/MANTRUN-181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Boué closed MANTRUN-181. -- Resolution: Fixed Assignee: Guillaume Boué Fix Version/s: 3.0.0

[jira] [Closed] (MANTRUN-203) Upgrade to maven-plugins 30

2017-06-06 Thread JIRA
[ https://issues.apache.org/jira/browse/MANTRUN-203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Boué closed MANTRUN-203. -- Resolution: Fixed Fix Version/s: 3.0.0 > Upgrade to maven-plugins

[jira] [Closed] (MANTRUN-172) Properties passed to Maven as -D don't get passed to invocations when a profile sets the same property

2017-06-06 Thread JIRA
[ https://issues.apache.org/jira/browse/MANTRUN-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Boué closed MANTRUN-172. -- Resolution: Fixed Assignee: Guillaume Boué Fix Version/s: 3.0.0 > Propert

[jira] [Commented] (MDEPLOY-221) deploy generates wrong timestamps in maven-metadata.xml

2017-06-08 Thread JIRA
[ https://issues.apache.org/jira/browse/MDEPLOY-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16043573#comment-16043573 ] Guillaume Boué commented on MDEPLOY-221: [~vvandens] I reproduced the i

[jira] [Comment Edited] (MDEPLOY-221) deploy generates wrong timestamps in maven-metadata.xml

2017-06-08 Thread JIRA
[ https://issues.apache.org/jira/browse/MDEPLOY-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16043573#comment-16043573 ] Guillaume Boué edited comment on MDEPLOY-221 at 6/8/17 11:1

<    3   4   5   6   7   8   9   10   11   12   >