[GitHub] sormuras commented on a change in pull request #209: Surefire 1614

2018-12-12 Thread GitBox
sormuras commented on a change in pull request #209: Surefire 1614 URL: https://github.com/apache/maven-surefire/pull/209#discussion_r241289308 ## File path: surefire-its/src/test/resources/surefire-1614-stream-corruption/src/test/java/com/example/demo/CustomRunner.java ##

[GitHub] Tibor17 commented on a change in pull request #209: Surefire 1614

2018-12-12 Thread GitBox
Tibor17 commented on a change in pull request #209: Surefire 1614 URL: https://github.com/apache/maven-surefire/pull/209#discussion_r241295288 ## File path: surefire-providers/surefire-junit-platform/src/main/java/org/apache/maven/surefire/junitplatform/JUnitPlatformProvider.java #

[GitHub] Tibor17 commented on a change in pull request #209: Surefire 1614

2018-12-12 Thread GitBox
Tibor17 commented on a change in pull request #209: Surefire 1614 URL: https://github.com/apache/maven-surefire/pull/209#discussion_r241294891 ## File path: surefire-providers/surefire-junit-platform/src/main/java/org/apache/maven/surefire/junitplatform/JUnitPlatformProvider.java #

[GitHub] Tibor17 commented on a change in pull request #209: Surefire 1614

2018-12-12 Thread GitBox
Tibor17 commented on a change in pull request #209: Surefire 1614 URL: https://github.com/apache/maven-surefire/pull/209#discussion_r241294344 ## File path: surefire-its/src/test/resources/surefire-1614-stream-corruption/src/test/java/com/example/demo/CustomRunner.java ##

[GitHub] sormuras commented on a change in pull request #209: Surefire 1614

2018-12-12 Thread GitBox
sormuras commented on a change in pull request #209: Surefire 1614 URL: https://github.com/apache/maven-surefire/pull/209#discussion_r241293575 ## File path: surefire-its/src/test/resources/surefire-1614-stream-corruption/src/test/java/com/example/demo/CustomRunner.java ##

[GitHub] Tibor17 commented on a change in pull request #209: Surefire 1614

2018-12-12 Thread GitBox
Tibor17 commented on a change in pull request #209: Surefire 1614 URL: https://github.com/apache/maven-surefire/pull/209#discussion_r241292709 ## File path: surefire-its/src/test/resources/surefire-1614-stream-corruption/src/test/java/com/example/demo/CustomRunner.java ##

[GitHub] sormuras commented on a change in pull request #209: Surefire 1614

2018-12-12 Thread GitBox
sormuras commented on a change in pull request #209: Surefire 1614 URL: https://github.com/apache/maven-surefire/pull/209#discussion_r241289930 ## File path: surefire-providers/surefire-junit-platform/src/main/java/org/apache/maven/surefire/junitplatform/JUnitPlatformProvider.java

[GitHub] sormuras commented on a change in pull request #209: Surefire 1614

2018-12-12 Thread GitBox
sormuras commented on a change in pull request #209: Surefire 1614 URL: https://github.com/apache/maven-surefire/pull/209#discussion_r241289308 ## File path: surefire-its/src/test/resources/surefire-1614-stream-corruption/src/test/java/com/example/demo/CustomRunner.java ##

[GitHub] eolivelli commented on a change in pull request #209: Surefire 1614

2018-12-12 Thread GitBox
eolivelli commented on a change in pull request #209: Surefire 1614 URL: https://github.com/apache/maven-surefire/pull/209#discussion_r241287212 ## File path: surefire-its/src/test/resources/surefire-1614-stream-corruption/src/test/java/com/example/demo/CustomRunner.java ##

[GitHub] eolivelli commented on a change in pull request #209: Surefire 1614

2018-12-12 Thread GitBox
eolivelli commented on a change in pull request #209: Surefire 1614 URL: https://github.com/apache/maven-surefire/pull/209#discussion_r241287212 ## File path: surefire-its/src/test/resources/surefire-1614-stream-corruption/src/test/java/com/example/demo/CustomRunner.java ##

[GitHub] eolivelli commented on a change in pull request #209: Surefire 1614

2018-12-12 Thread GitBox
eolivelli commented on a change in pull request #209: Surefire 1614 URL: https://github.com/apache/maven-surefire/pull/209#discussion_r241286208 ## File path: surefire-providers/surefire-junit-platform/src/main/java/org/apache/maven/surefire/junitplatform/JUnitPlatformProvider.java

[jira] [Commented] (MNGSITE-360) upgrade archetype version to 1.4 to support Java 11

2018-12-12 Thread Hudson (JIRA)
[ https://issues.apache.org/jira/browse/MNGSITE-360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16719784#comment-16719784 ] Hudson commented on MNGSITE-360: Build succeeded in Jenkins: Maven TLP » maven-site » ma

[GitHub] pes2009j commented on issue #209: Surefire 1614

2018-12-12 Thread GitBox
pes2009j commented on issue #209: Surefire 1614 URL: https://github.com/apache/maven-surefire/pull/209#issuecomment-446790063 ipad This is an automated message from the Apache Git Service. To respond to the message, please lo

[GitHub] Tibor17 commented on a change in pull request #209: Surefire 1614

2018-12-12 Thread GitBox
Tibor17 commented on a change in pull request #209: Surefire 1614 URL: https://github.com/apache/maven-surefire/pull/209#discussion_r241228365 ## File path: surefire-providers/surefire-junit-platform/src/main/java/org/apache/maven/surefire/junitplatform/JUnitPlatformProvider.java #

[jira] [Comment Edited] (MNG-6502) More performant AbstractZipArchiver when maven module contains lots of big resources

2018-12-12 Thread Hoa Phan (JIRA)
[ https://issues.apache.org/jira/browse/MNG-6502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16701385#comment-16701385 ] Hoa Phan edited comment on MNG-6502 at 12/12/18 10:50 PM: -- sorry [

[GitHub] Tibor17 commented on a change in pull request #209: Surefire 1614

2018-12-12 Thread GitBox
Tibor17 commented on a change in pull request #209: Surefire 1614 URL: https://github.com/apache/maven-surefire/pull/209#discussion_r241212544 ## File path: surefire-its/src/test/resources/surefire-1614-stream-corruption/src/test/java/com/example/demo/CustomRunner.java ##

[GitHub] Tibor17 commented on a change in pull request #209: Surefire 1614

2018-12-12 Thread GitBox
Tibor17 commented on a change in pull request #209: Surefire 1614 URL: https://github.com/apache/maven-surefire/pull/209#discussion_r241212544 ## File path: surefire-its/src/test/resources/surefire-1614-stream-corruption/src/test/java/com/example/demo/CustomRunner.java ##

[GitHub] Tibor17 commented on a change in pull request #209: Surefire 1614

2018-12-12 Thread GitBox
Tibor17 commented on a change in pull request #209: Surefire 1614 URL: https://github.com/apache/maven-surefire/pull/209#discussion_r241212544 ## File path: surefire-its/src/test/resources/surefire-1614-stream-corruption/src/test/java/com/example/demo/CustomRunner.java ##

[GitHub] Tibor17 commented on a change in pull request #209: Surefire 1614

2018-12-12 Thread GitBox
Tibor17 commented on a change in pull request #209: Surefire 1614 URL: https://github.com/apache/maven-surefire/pull/209#discussion_r241210839 ## File path: surefire-providers/surefire-junit-platform/src/main/java/org/apache/maven/surefire/junitplatform/JUnitPlatformProvider.java #

[GitHub] Tibor17 commented on a change in pull request #209: Surefire 1614

2018-12-12 Thread GitBox
Tibor17 commented on a change in pull request #209: Surefire 1614 URL: https://github.com/apache/maven-surefire/pull/209#discussion_r241210026 ## File path: surefire-providers/surefire-junit-platform/src/main/java/org/apache/maven/surefire/junitplatform/JUnitPlatformProvider.java #

[jira] [Commented] (SUREFIRE-1614) JUnit Runner that writes to System.out corrupts Surefire's STDOUT when using JUnit's Vintage Engine

2018-12-12 Thread Christian Stein (JIRA)
[ https://issues.apache.org/jira/browse/SUREFIRE-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16719502#comment-16719502 ] Christian Stein commented on SUREFIRE-1614: --- Potential fix at PR https://git

[GitHub] sormuras opened a new pull request #209: Surefire 1614

2018-12-12 Thread GitBox
sormuras opened a new pull request #209: Surefire 1614 URL: https://github.com/apache/maven-surefire/pull/209 Capture system stream earlier to prevent its corruption. This is an automated message from the Apache Git Service. T

[jira] [Commented] (SUREFIRE-1614) JUnit Runner that writes to System.out corrupts Surefire's STDOUT when using JUnit's Vintage Engine

2018-12-12 Thread Tibor Digana (JIRA)
[ https://issues.apache.org/jira/browse/SUREFIRE-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16719490#comment-16719490 ] Tibor Digana commented on SUREFIRE-1614: [~sor] IMHO this is obvious that the

[jira] [Updated] (MPOM-209) The issueManagement entry points to wrong location.

2018-12-12 Thread Robert Scholte (JIRA)
[ https://issues.apache.org/jira/browse/MPOM-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MPOM-209: Labels: up-for-grabs (was: ) > The issueManagement entry points to wrong location. > ---

[GitHub] rfscholte commented on issue #2: Update maven-compiler-plugin to 3.8.0

2018-12-12 Thread GitBox
rfscholte commented on issue #2: Update maven-compiler-plugin to 3.8.0 URL: https://github.com/apache/maven-apache-parent/pull/2#issuecomment-446748787 Release notes will be based on Jira: this PR is related to https://issues.apache.org/jira/browse/MPOM-207

[GitHub] eolivelli commented on issue #47: [MENFORCER-323] - Improve output of "Some plugins are missing valid versions" error

2018-12-12 Thread GitBox
eolivelli commented on issue #47: [MENFORCER-323] - Improve output of "Some plugins are missing valid versions" error URL: https://github.com/apache/maven-enforcer/pull/47#issuecomment-446729703 Thank you. We are not (yet) using that github way of closing prs as our primary system is on

[GitHub] jsoref commented on issue #47: [MENFORCER-323] - Improve output of "Some plugins are missing valid versions" error

2018-12-12 Thread GitBox
jsoref commented on issue #47: [MENFORCER-323] - Improve output of "Some plugins are missing valid versions" error URL: https://github.com/apache/maven-enforcer/pull/47#issuecomment-446726427 For reference, this was merged as 5ac7679

[GitHub] jsoref commented on issue #47: [MENFORCER-323] - Improve output of "Some plugins are missing valid versions" error

2018-12-12 Thread GitBox
jsoref commented on issue #47: [MENFORCER-323] - Improve output of "Some plugins are missing valid versions" error URL: https://github.com/apache/maven-enforcer/pull/47#issuecomment-446726239 I'm closing this. I guess I should have had "closes #47" in my commit message to get it to auto-cl

[GitHub] jsoref closed pull request #47: [MENFORCER-323] - Improve output of "Some plugins are missing valid versions" error

2018-12-12 Thread GitBox
jsoref closed pull request #47: [MENFORCER-323] - Improve output of "Some plugins are missing valid versions" error URL: https://github.com/apache/maven-enforcer/pull/47 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the

[GitHub] jsoref commented on issue #48: [MENFORCER-324] - Shouldn't we use System.lineSeparator() instead?

2018-12-12 Thread GitBox
jsoref commented on issue #48: [MENFORCER-324] - Shouldn't we use System.lineSeparator() instead? URL: https://github.com/apache/maven-enforcer/pull/48#issuecomment-446725942 @eolivelli: rebased, but if you guys aren't particularly certain you want to take it, I really don't want to push t

[jira] [Closed] (MSHADE-305) Filters are merged by index, not by artifactId

2018-12-12 Thread Robert Scholte (JIRA)
[ https://issues.apache.org/jira/browse/MSHADE-305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MSHADE-305. - Resolution: Not A Problem Assignee: Robert Scholte When the pom-files are inherited, Maven

[jira] [Commented] (SUREFIRE-1496) Dump file error for java.lang.module.ResolutionException

2018-12-12 Thread Tibor Digana (JIRA)
[ https://issues.apache.org/jira/browse/SUREFIRE-1496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16719343#comment-16719343 ] Tibor Digana commented on SUREFIRE-1496: [~scolebou...@joda.org] [~earcam] The

[jira] [Assigned] (SUREFIRE-1614) JUnit Runner that writes to System.out corrupts Surefire's STDOUT when using JUnit's Vintage Engine

2018-12-12 Thread Christian Stein (JIRA)
[ https://issues.apache.org/jira/browse/SUREFIRE-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Stein reassigned SUREFIRE-1614: - Assignee: Christian Stein > JUnit Runner that writes to System.out corrupts S

[jira] [Commented] (SUREFIRE-1614) JUnit Runner that writes to System.out corrupts Surefire's STDOUT when using JUnit's Vintage Engine

2018-12-12 Thread Christian Stein (JIRA)
[ https://issues.apache.org/jira/browse/SUREFIRE-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16719344#comment-16719344 ] Christian Stein commented on SUREFIRE-1614: --- Thanks for raising the issue, [

[jira] [Commented] (MENFORCER-323) Improve output in case of "Some plugins are missing valid versions" error

2018-12-12 Thread Hudson (JIRA)
[ https://issues.apache.org/jira/browse/MENFORCER-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16719296#comment-16719296 ] Hudson commented on MENFORCER-323: -- Build succeeded in Jenkins: Maven TLP » maven-enf

[GitHub] andretadeu commented on issue #2: [MJMOD-8] NullPointerException on create

2018-12-12 Thread GitBox
andretadeu commented on issue #2: [MJMOD-8] NullPointerException on create URL: https://github.com/apache/maven-jmod-plugin/pull/2#issuecomment-446694864 Of course, I have two working examples: The first one I created a multi-module Maven project where I generated both JAR and JMOD f

[GitHub] eolivelli commented on issue #48: [MENFORCER-324] - Shouldn't we use System.lineSeparator() instead?

2018-12-12 Thread GitBox
eolivelli commented on issue #48: [MENFORCER-324] - Shouldn't we use System.lineSeparator() instead? URL: https://github.com/apache/maven-enforcer/pull/48#issuecomment-446691000 @jsoref can you please rebase to latest master ? What about changing the title and commit message and the

[GitHub] eolivelli commented on issue #47: [MENFORCER-323] - Improve output of "Some plugins are missing valid versions" error

2018-12-12 Thread GitBox
eolivelli commented on issue #47: [MENFORCER-323] - Improve output of "Some plugins are missing valid versions" error URL: https://github.com/apache/maven-enforcer/pull/47#issuecomment-446689614 merged to master. thank you @jsoref ---

[GitHub] Tibor17 commented on issue #208: Update StatelessXmlReporter.java

2018-12-12 Thread GitBox
Tibor17 commented on issue #208: Update StatelessXmlReporter.java URL: https://github.com/apache/maven-surefire/pull/208#issuecomment-446678392 @lanlingxueyu If you want to have a fix like this, subscribe in Jira (see the link in parent POM), create an issue as a feature, name the commi

[jira] [Assigned] (MENFORCER-324) Shouldn't we use System.lineSeparator() instead of \n ?

2018-12-12 Thread Karl Heinz Marbaise (JIRA)
[ https://issues.apache.org/jira/browse/MENFORCER-324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise reassigned MENFORCER-324: - Assignee: (was: Karl Heinz Marbaise) > Shouldn't we use System.li

[jira] [Assigned] (MENFORCER-324) Shouldn't we use System.lineSeparator() instead of \n ?

2018-12-12 Thread Karl Heinz Marbaise (JIRA)
[ https://issues.apache.org/jira/browse/MENFORCER-324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise reassigned MENFORCER-324: - Assignee: Karl Heinz Marbaise > Shouldn't we use System.lineSeparator

[jira] [Updated] (MENFORCER-324) Shouldn't we use System.lineSeparator() instead of \n ?

2018-12-12 Thread Karl Heinz Marbaise (JIRA)
[ https://issues.apache.org/jira/browse/MENFORCER-324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MENFORCER-324: -- Issue Type: Improvement (was: Bug) > Shouldn't we use System.lineSeparator(

[jira] [Commented] (MASSEMBLY-861) exclusion * also packaged

2018-12-12 Thread Robert Scholte (JIRA)
[ https://issues.apache.org/jira/browse/MASSEMBLY-861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16719246#comment-16719246 ] Robert Scholte commented on MASSEMBLY-861: -- Only maven-developers can be assi

[GitHub] khmarbaise commented on issue #7: [MCHECKSTYLE-357] - Allow inline configuration for reporting

2018-12-12 Thread GitBox
khmarbaise commented on issue #7: [MCHECKSTYLE-357] - Allow inline configuration for reporting URL: https://github.com/apache/maven-checkstyle-plugin/pull/7#issuecomment-446674789 The only thing which should not be done is the LICENSE.txt file cause the license file are automatically adde

[GitHub] eolivelli commented on issue #47: [MENFORCER-323] - Improve output of "Some plugins are missing valid versions" error

2018-12-12 Thread GitBox
eolivelli commented on issue #47: [MENFORCER-323] - Improve output of "Some plugins are missing valid versions" error URL: https://github.com/apache/maven-enforcer/pull/47#issuecomment-446674001 I am merging this This is an a

[jira] [Commented] (MASSEMBLY-861) exclusion * also packaged

2018-12-12 Thread Enrico Olivelli (JIRA)
[ https://issues.apache.org/jira/browse/MASSEMBLY-861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16719207#comment-16719207 ] Enrico Olivelli commented on MASSEMBLY-861: --- I am hitting this problem. [~r

[jira] [Commented] (MASSEMBLY-874) maven-assembly plugin always downloads dependencies from net

2018-12-12 Thread Enrico Olivelli (JIRA)
[ https://issues.apache.org/jira/browse/MASSEMBLY-874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16719203#comment-16719203 ] Enrico Olivelli commented on MASSEMBLY-874: --- Same issue from my side. I wil

[GitHub] khmarbaise commented on issue #2: [MJMOD-8] NullPointerException on create

2018-12-12 Thread GitBox
khmarbaise commented on issue #2: [MJMOD-8] NullPointerException on create URL: https://github.com/apache/maven-jmod-plugin/pull/2#issuecomment-44555 First thanks for your contribution but on the other hand I'm thinking about this use case which looks to me like a different goal in the

[jira] [Comment Edited] (MASSEMBLY-874) maven-assembly plugin always downloads dependencies from net

2018-12-12 Thread Enrico Olivelli (JIRA)
[ https://issues.apache.org/jira/browse/MASSEMBLY-874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16719203#comment-16719203 ] Enrico Olivelli edited comment on MASSEMBLY-874 at 12/12/18 5:02 PM: ---

[GitHub] andretadeu opened a new pull request #2: [MJMOD-8] NullPointerException on create

2018-12-12 Thread GitBox
andretadeu opened a new pull request #2: [MJMOD-8] NullPointerException on create URL: https://github.com/apache/maven-jmod-plugin/pull/2 Hi, I created this pull request to fulfill to address the need to set **--class-path** parameter from _jmod create_, because it offers the possi

[jira] [Commented] (ARCHETYPE-531) NullPointerException when module not specified or config empty in EAR plugin

2018-12-12 Thread Marco Rothe (JIRA)
[ https://issues.apache.org/jira/browse/ARCHETYPE-531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16719166#comment-16719166 ] Marco Rothe commented on ARCHETYPE-531: --- I encountered the same problem today: T

[jira] [Updated] (MJAR-259) Archiving to jar is very slow

2018-12-12 Thread Karl Heinz Marbaise (JIRA)
[ https://issues.apache.org/jira/browse/MJAR-259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MJAR-259: - Fix Version/s: 3.1.2 > Archiving to jar is very slow > - > >

[jira] [Assigned] (MJAR-259) Archiving to jar is very slow

2018-12-12 Thread Karl Heinz Marbaise (JIRA)
[ https://issues.apache.org/jira/browse/MJAR-259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise reassigned MJAR-259: Assignee: Karl Heinz Marbaise > Archiving to jar is very slow >

[jira] [Comment Edited] (MNG-4839) plugin dependencies not resolved form repositories

2018-12-12 Thread Matt Parker (JIRA)
[ https://issues.apache.org/jira/browse/MNG-4839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16719095#comment-16719095 ] Matt Parker edited comment on MNG-4839 at 12/12/18 4:16 PM: See

[jira] [Updated] (MSHARED-709) Upgrade maven 3.X only

2018-12-12 Thread Karl Heinz Marbaise (JIRA)
[ https://issues.apache.org/jira/browse/MSHARED-709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MSHARED-709: Component/s: maven-dependency-analyzer > Upgrade maven 3.X only >

[jira] [Created] (MPIR-378) NPE during site generation when module packaging is 'bundle'

2018-12-12 Thread Alexey Markevich (JIRA)
Alexey Markevich created MPIR-378: - Summary: NPE during site generation when module packaging is 'bundle' Key: MPIR-378 URL: https://issues.apache.org/jira/browse/MPIR-378 Project: Maven Project Info

[jira] [Commented] (MNG-4839) plugin dependencies not resolved form repositories

2018-12-12 Thread Matt Parker (JIRA)
[ https://issues.apache.org/jira/browse/MNG-4839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16719095#comment-16719095 ] Matt Parker commented on MNG-4839: -- Seems like how this works is too constrained. I'm havi

[GitHub] eolivelli commented on issue #7: [MCHECKSTYLE-357] - Allow inline configuration for reporting

2018-12-12 Thread GitBox
eolivelli commented on issue #7: [MCHECKSTYLE-357] - Allow inline configuration for reporting URL: https://github.com/apache/maven-checkstyle-plugin/pull/7#issuecomment-446627103 Great. I will wait for approval from another committer and then merge this patch soon Thank you --

[GitHub] Serranya commented on issue #7: [MCHECKSTYLE-357] - Allow inline configuration for reporting

2018-12-12 Thread GitBox
Serranya commented on issue #7: [MCHECKSTYLE-357] - Allow inline configuration for reporting URL: https://github.com/apache/maven-checkstyle-plugin/pull/7#issuecomment-446626385 The CI build succeeded. This is an automated m

[GitHub] eolivelli commented on issue #7: [MCHECKSTYLE-357] - Allow inline configuration for reporting

2018-12-12 Thread GitBox
eolivelli commented on issue #7: [MCHECKSTYLE-357] - Allow inline configuration for reporting URL: https://github.com/apache/maven-checkstyle-plugin/pull/7#issuecomment-446620421 Here it is https://builds.apache.org/job/maven-box/job/maven-checkstyle-plugin/job/MCHECKSTYLE-357/2/

[GitHub] eolivelli commented on issue #7: [MCHECKSTYLE-357] - Allow inline configuration for reporting

2018-12-12 Thread GitBox
eolivelli commented on issue #7: [MCHECKSTYLE-357] - Allow inline configuration for reporting URL: https://github.com/apache/maven-checkstyle-plugin/pull/7#issuecomment-446618962 sure This is an automated message from the Ap

[GitHub] Serranya commented on issue #7: [MCHECKSTYLE-357] - Allow inline configuration for reporting

2018-12-12 Thread GitBox
Serranya commented on issue #7: [MCHECKSTYLE-357] - Allow inline configuration for reporting URL: https://github.com/apache/maven-checkstyle-plugin/pull/7#issuecomment-446618457 @eolivelli Can you start the CI build again? The problem should be fixed now. -

[GitHub] eolivelli commented on issue #7: [MCHECKSTYLE-357] - Allow inline configuration for reporting

2018-12-12 Thread GitBox
eolivelli commented on issue #7: [MCHECKSTYLE-357] - Allow inline configuration for reporting URL: https://github.com/apache/maven-checkstyle-plugin/pull/7#issuecomment-446610632 Good catch This is an automated message from

[GitHub] Serranya commented on issue #7: [MCHECKSTYLE-357] - Allow inline configuration for reporting

2018-12-12 Thread GitBox
Serranya commented on issue #7: [MCHECKSTYLE-357] - Allow inline configuration for reporting URL: https://github.com/apache/maven-checkstyle-plugin/pull/7#issuecomment-446610234 Ahh, the checkstyle version I referenced in the IT pom is too new: ``` [ERROR] Failed to execute goal org

[GitHub] Serranya commented on issue #7: [MCHECKSTYLE-357] - Allow inline configuration for reporting

2018-12-12 Thread GitBox
Serranya commented on issue #7: [MCHECKSTYLE-357] - Allow inline configuration for reporting URL: https://github.com/apache/maven-checkstyle-plugin/pull/7#issuecomment-446609685 I was able to reproduce them as well. This is

[GitHub] eolivelli commented on issue #7: [MCHECKSTYLE-357] - Allow inline configuration for reporting

2018-12-12 Thread GitBox
eolivelli commented on issue #7: [MCHECKSTYLE-357] - Allow inline configuration for reporting URL: https://github.com/apache/maven-checkstyle-plugin/pull/7#issuecomment-446607487 I have this error on jdk7, on linux, locally: ``` INFO] Building: MCHECKSTYLE-357/pom.xml [INFO] r

[GitHub] eolivelli commented on issue #7: [MCHECKSTYLE-357] - Allow inline configuration for reporting

2018-12-12 Thread GitBox
eolivelli commented on issue #7: [MCHECKSTYLE-357] - Allow inline configuration for reporting URL: https://github.com/apache/maven-checkstyle-plugin/pull/7#issuecomment-446602006 I am trying too This is an automated message

[GitHub] Serranya edited a comment on issue #7: [MCHECKSTYLE-357] - Allow inline configuration for reporting

2018-12-12 Thread GitBox
Serranya edited a comment on issue #7: [MCHECKSTYLE-357] - Allow inline configuration for reporting URL: https://github.com/apache/maven-checkstyle-plugin/pull/7#issuecomment-446601597 Yeah I ran them locally with JDK11 and * Maven 3.6.0 * Maven 3.5.4 * Maven 3.2.5 I wil

[GitHub] Serranya edited a comment on issue #7: [MCHECKSTYLE-357] - Allow inline configuration for reporting

2018-12-12 Thread GitBox
Serranya edited a comment on issue #7: [MCHECKSTYLE-357] - Allow inline configuration for reporting URL: https://github.com/apache/maven-checkstyle-plugin/pull/7#issuecomment-446601597 Yeah I ran them locally with JDK11 and * Maven 3.6.0 * Maven 3.5.4 * Maven 3.2.5 I will tr

[GitHub] Serranya commented on issue #7: [MCHECKSTYLE-357] - Allow inline configuration for reporting

2018-12-12 Thread GitBox
Serranya commented on issue #7: [MCHECKSTYLE-357] - Allow inline configuration for reporting URL: https://github.com/apache/maven-checkstyle-plugin/pull/7#issuecomment-446601597 Yeah i ran them locally with JDK11 and * Maven 3.6.0 * Maven 3.5.4 * Maven 3.2.5 I will try it ag

[GitHub] eolivelli commented on issue #7: [MCHECKSTYLE-357] - Allow inline configuration for reporting

2018-12-12 Thread GitBox
eolivelli commented on issue #7: [MCHECKSTYLE-357] - Allow inline configuration for reporting URL: https://github.com/apache/maven-checkstyle-plugin/pull/7#issuecomment-446599928 @Serranya did you run all the integration tests locally ? `mvn clean verify -Prun-its` It seem

[GitHub] Serranya commented on issue #7: [MCHECKSTYLE-357] - Allow inline configuration for reporting

2018-12-12 Thread GitBox
Serranya commented on issue #7: [MCHECKSTYLE-357] - Allow inline configuration for reporting URL: https://github.com/apache/maven-checkstyle-plugin/pull/7#issuecomment-446590794 Is there a way to see the integration test maven output of the MCHECKSTYLE-357 test? -

[GitHub] rnveach commented on issue #7: [MCHECKSTYLE-357] - Allow inline configuration for reporting

2018-12-12 Thread GitBox
rnveach commented on issue #7: [MCHECKSTYLE-357] - Allow inline configuration for reporting URL: https://github.com/apache/maven-checkstyle-plugin/pull/7#issuecomment-446565653 Looking at the full console output, you can see a failure https://builds.apache.org/job/maven-box/job/maven-c

[GitHub] rnveach edited a comment on issue #7: [MCHECKSTYLE-357] - Allow inline configuration for reporting

2018-12-12 Thread GitBox
rnveach edited a comment on issue #7: [MCHECKSTYLE-357] - Allow inline configuration for reporting URL: https://github.com/apache/maven-checkstyle-plugin/pull/7#issuecomment-446565653 Looking at the full console output, you can see a failure https://builds.apache.org/job/maven-box/job/

[jira] [Created] (MSHADE-305) Filters are merged by index, not by artifactId

2018-12-12 Thread Chesnay Schepler (JIRA)
Chesnay Schepler created MSHADE-305: --- Summary: Filters are merged by index, not by artifactId Key: MSHADE-305 URL: https://issues.apache.org/jira/browse/MSHADE-305 Project: Maven Shade Plugin

[jira] [Commented] (MCHECKSTYLE-357) also allow inline configuration for reporting

2018-12-12 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/MCHECKSTYLE-357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16718733#comment-16718733 ] ASF GitHub Bot commented on MCHECKSTYLE-357: Serranya commented on issue

[GitHub] Serranya commented on issue #7: [MCHECKSTYLE-357] - Allow inline configuration for reporting

2018-12-12 Thread GitBox
Serranya commented on issue #7: [MCHECKSTYLE-357] - Allow inline configuration for reporting URL: https://github.com/apache/maven-checkstyle-plugin/pull/7#issuecomment-446535667 I don't really understand why the CI build failed. I looked into the console log and it seems like the ma

[jira] [Commented] (MNG-5965) Parallel build multiplies work if multiple goals are given

2018-12-12 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/MNG-5965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16718722#comment-16718722 ] ASF GitHub Bot commented on MNG-5965: - FrzMe commented on issue #125: [MNG-5965] Parall

[GitHub] FrzMe commented on issue #125: [MNG-5965] Parallel build multiplies work if multiple goals are given

2018-12-12 Thread GitBox
FrzMe commented on issue #125: [MNG-5965] Parallel build multiplies work if multiple goals are given URL: https://github.com/apache/maven/pull/125#issuecomment-446532810 @michael-o I would be happy if you could have a look! Thank you so much