[jira] [Commented] (MRELEASE-909) Add workItem/task support for scm deliver

[ https://issues.apache.org/jira/browse/MRELEASE-909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15656588#comment-15656588 ] Daniel Reghin commented on MRELEASE-909: Chris, this improvement has been releas

[jira] [Commented] (SUREFIRE-1302) The forked VM terminated without properly saying goodbye. VM crash or System.exit called?

[ https://issues.apache.org/jira/browse/SUREFIRE-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15656708#comment-15656708 ] Yuriy commented on SUREFIRE-1302: - Originally there is a situation when the process is

[jira] [Commented] (SUREFIRE-1302) The forked VM terminated without properly saying goodbye. VM crash or System.exit called?

[ https://issues.apache.org/jira/browse/SUREFIRE-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15656805#comment-15656805 ] Michael Osipov commented on SUREFIRE-1302: -- To fully understand the issue: the

[jira] [Commented] (SUREFIRE-1302) The forked VM terminated without properly saying goodbye. VM crash or System.exit called?

[ https://issues.apache.org/jira/browse/SUREFIRE-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15656857#comment-15656857 ] Yuriy Zaplavnov commented on SUREFIRE-1302: --- Correct. You understand the case

[jira] [Comment Edited] (SUREFIRE-1302) The forked VM terminated without properly saying goodbye. VM crash or System.exit called?

[ https://issues.apache.org/jira/browse/SUREFIRE-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15656857#comment-15656857 ] Yuriy Zaplavnov edited comment on SUREFIRE-1302 at 11/11/16 11:41 AM: ---

[jira] [Commented] (SUREFIRE-1302) The forked VM terminated without properly saying goodbye. VM crash or System.exit called?

[ https://issues.apache.org/jira/browse/SUREFIRE-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15656878#comment-15656878 ] Michael Osipov commented on SUREFIRE-1302: -- I think your problem can be solved

[jira] [Commented] (SUREFIRE-859) Exception in thread "TreadedStreamConsumer" java.lang.RuntimeException during GC

[ https://issues.apache.org/jira/browse/SUREFIRE-859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15656891#comment-15656891 ] ASF GitHub Bot commented on SUREFIRE-859: - Github user Tibor17 commented on the

[jira] [Updated] (SUREFIRE-1302) Surefire does not wait long enough for the forked VM and assues it to be dead

[ https://issues.apache.org/jira/browse/SUREFIRE-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuriy Zaplavnov updated SUREFIRE-1302: -- Summary: Surefire does not wait long enough for the forked VM and assues it to be dea

[jira] [Updated] (SUREFIRE-1302) Surefire does not wait long enough for the forked VM and assumes it to be dead

[ https://issues.apache.org/jira/browse/SUREFIRE-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated SUREFIRE-1302: - Summary: Surefire does not wait long enough for the forked VM and assumes it to be dead

[jira] [Comment Edited] (SUREFIRE-1302) Surefire does not wait long enough for the forked VM and assumes it to be dead

[ https://issues.apache.org/jira/browse/SUREFIRE-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15656878#comment-15656878 ] Michael Osipov edited comment on SUREFIRE-1302 at 11/11/16 12:10 PM:

[jira] [Updated] (SUREFIRE-1302) Surefire does not wait long enough for the forked VM and assumes it to be dead

[ https://issues.apache.org/jira/browse/SUREFIRE-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuriy Zaplavnov updated SUREFIRE-1302: -- Issue Type: Request (was: Bug) > Surefire does not wait long enough for the forked V

[jira] [Commented] (SUREFIRE-1302) Surefire does not wait long enough for the forked VM and assumes it to be dead

[ https://issues.apache.org/jira/browse/SUREFIRE-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15656928#comment-15656928 ] Yuriy Zaplavnov commented on SUREFIRE-1302: --- Thanks for your assistance! Just

[jira] [Created] (MNG-6111) incorrect text in help:describe for cmd

aaa created MNG-6111: Summary: incorrect text in help:describe for cmd Key: MNG-6111 URL: https://issues.apache.org/jira/browse/MNG-6111 Project: Maven Issue Type: Bug Components: Plugins and L

[jira] [Commented] (SUREFIRE-1302) Surefire does not wait long enough for the forked VM and assumes it to be dead

[ https://issues.apache.org/jira/browse/SUREFIRE-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15656967#comment-15656967 ] Michael Osipov commented on SUREFIRE-1302: -- Not exactly how I expected. This i

[jira] [Commented] (MRELEASE-966) release plugin does not respect "mvn -f"

[ https://issues.apache.org/jira/browse/MRELEASE-966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15657343#comment-15657343 ] Guillaume Boué commented on MRELEASE-966: - Fixed in [r1769304|http://svn.apache.

Re: [jira] [Created] (MNG-6111) incorrect text in help:describe for cmd

This issue is for the Maven Help Plugin. Can someone move it to the MPH JIRA? Thanks, Guillaume Le 11/11/2016 à 13:23, aaa (JIRA) a écrit : aaa created MNG-6111: Summary: incorrect text in help:describe for cmd Key: MNG-6111

[jira] [Closed] (MRELEASE-966) release plugin does not respect "mvn -f"

[ https://issues.apache.org/jira/browse/MRELEASE-966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Boué closed MRELEASE-966. --- Resolution: Fixed Assignee: Guillaume Boué Fix Version/s: 3.0.0 > release pl

[jira] [Moved] (MPH-121) incorrect text in help:describe for cmd

[ https://issues.apache.org/jira/browse/MPH-121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise moved MNG-6111 to MPH-121: -- Affects Version/s: (was: 3.3.9) 2.2 Co

[jira] [Commented] (MPH-120) Migrate plugin to Maven 3.0

[ https://issues.apache.org/jira/browse/MPH-120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15657559#comment-15657559 ] Guillaume Boué commented on MPH-120: Fixed in [r1769319|http://svn.apache.org/viewvc?rev=

[jira] [Commented] (MPH-120) Migrate plugin to Maven 3.0

[ https://issues.apache.org/jira/browse/MPH-120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15657606#comment-15657606 ] Hudson commented on MPH-120: SUCCESS: Integrated in Jenkins build maven-plugins #7593 (See [http

[jira] [Commented] (MPH-120) Migrate plugin to Maven 3.0

[ https://issues.apache.org/jira/browse/MPH-120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15657740#comment-15657740 ] Michael Osipov commented on MPH-120: You are awesome, great work. This is something I hav

[jira] [Commented] (MPH-121) incorrect text in help:describe for cmd

[ https://issues.apache.org/jira/browse/MPH-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1565#comment-1565 ] Guillaume Boué commented on MPH-121: Yes, this could be phrased better. I'm thinking of a

[jira] [Commented] (SUREFIRE-1303) The forked VM terminated without properly saying goodbye. VM crash or System.exit called?

[ https://issues.apache.org/jira/browse/SUREFIRE-1303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15657989#comment-15657989 ] Tibor Digana commented on SUREFIRE-1303: [~MarvinKRK] This happened to me as we

[jira] [Commented] (MRELEASE-966) release plugin does not respect "mvn -f"

[ https://issues.apache.org/jira/browse/MRELEASE-966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15658023#comment-15658023 ] Robert Scholte commented on MRELEASE-966: - I think that the reason for the old i

[jira] [Commented] (SUREFIRE-1302) Surefire does not wait long enough for the forked VM and assumes it to be dead

[ https://issues.apache.org/jira/browse/SUREFIRE-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15658028#comment-15658028 ] Tibor Digana commented on SUREFIRE-1302: [~xeagle] But this does not need PR. T

[jira] [Commented] (SUREFIRE-1302) Surefire does not wait long enough for the forked VM and assumes it to be dead

[ https://issues.apache.org/jira/browse/SUREFIRE-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15658051#comment-15658051 ] Tibor Digana commented on SUREFIRE-1302: [~xeagle] Please see this issue SUREFI

[jira] [Commented] (SUREFIRE-1301) baseDir system-property gets overridden by other builder threads if forking is disabled

[ https://issues.apache.org/jira/browse/SUREFIRE-1301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15658087#comment-15658087 ] Tibor Digana commented on SUREFIRE-1301: [~agudian] Hi Andreas, do you have any

[jira] [Reopened] (MNG-2478) add "resources-filtered" filtered resource directories to super POM

[ https://issues.apache.org/jira/browse/MNG-2478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schulte reopened MNG-2478: Assignee: (was: Christian Schulte) This has been reverted in 3.4 and postponed to model

[jira] [Updated] (MNG-2478) add "resources-filtered" filtered resource directories to super POM

[ https://issues.apache.org/jira/browse/MNG-2478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schulte updated MNG-2478: --- Fix Version/s: (was: 3.4.0) > add "resources-filtered" filtered resource directories to supe

[jira] [Reopened] (MNG-5940) Change the maven-source-plugin jar goal into jar-no-fork in Maven Super POM

[ https://issues.apache.org/jira/browse/MNG-5940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schulte reopened MNG-5940: Assignee: (was: Christian Schulte) This has been reverted in 3.4 and postponed to model

[jira] [Updated] (MNG-5940) Change the maven-source-plugin jar goal into jar-no-fork in Maven Super POM

[ https://issues.apache.org/jira/browse/MNG-5940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schulte updated MNG-5940: --- Fix Version/s: (was: 3.4.0) > Change the maven-source-plugin jar goal into jar-no-fork in Ma

[jira] [Reopened] (MNG-6054) Removal of super pom plugin management.

[ https://issues.apache.org/jira/browse/MNG-6054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schulte reopened MNG-6054: Assignee: (was: Christian Schulte) This has been reverted in 3.4 and postponed to model

[jira] [Updated] (MNG-6054) Removal of super pom plugin management.

[ https://issues.apache.org/jira/browse/MNG-6054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schulte updated MNG-6054: --- Fix Version/s: (was: 3.4.0) > Removal of super pom plugin management. >

[jira] [Commented] (MDEPLOY-211) uniqueVersion broken (if not supported, should be removed from doc, and warning printed)

[ https://issues.apache.org/jira/browse/MDEPLOY-211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15658125#comment-15658125 ] Guillaume Boué commented on MDEPLOY-211: The code and the docs have been cleaned

[jira] [Created] (MNG-6112) Central repository in the 4.0.0 super POM should declare update policy 'never'.

Christian Schulte created MNG-6112: -- Summary: Central repository in the 4.0.0 super POM should declare update policy 'never'. Key: MNG-6112 URL: https://issues.apache.org/jira/browse/MNG-6112 Project

[jira] [Created] (MNG-6113) Rename the 'Central Repository' to 'Maven Central Repository' in the 4.0.0 super POM.

Christian Schulte created MNG-6113: -- Summary: Rename the 'Central Repository' to 'Maven Central Repository' in the 4.0.0 super POM. Key: MNG-6113 URL: https://issues.apache.org/jira/browse/MNG-6113 P

[jira] [Closed] (MNG-6113) Rename the 'Central Repository' to 'Maven Central Repository' in the 4.0.0 super POM.

[ https://issues.apache.org/jira/browse/MNG-6113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schulte closed MNG-6113. -- Resolution: Fixed > Rename the 'Central Repository' to 'Maven Central Repository' in the 4.0.0 >

[jira] [Updated] (MNG-6113) Rename the 'Central Repository' to 'Maven Central Repository' in the 4.0.0 super POM.

[ https://issues.apache.org/jira/browse/MNG-6113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schulte updated MNG-6113: --- Fix Version/s: 3.4.0 > Rename the 'Central Repository' to 'Maven Central Repository' in the 4.0.

[jira] [Closed] (MNG-6112) Central repository in the 4.0.0 super POM should declare update policy 'never'.

[ https://issues.apache.org/jira/browse/MNG-6112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schulte closed MNG-6112. -- Resolution: Fixed > Central repository in the 4.0.0 super POM should declare update policy > 'nev

[jira] [Updated] (MNG-6112) Central repository in the 4.0.0 super POM should declare update policy 'never'.

[ https://issues.apache.org/jira/browse/MNG-6112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schulte updated MNG-6112: --- Fix Version/s: 3.4.0 > Central repository in the 4.0.0 super POM should declare update policy >

[jira] [Commented] (MNG-6112) Central repository in the 4.0.0 super POM should declare update policy 'never'.

[ https://issues.apache.org/jira/browse/MNG-6112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15658210#comment-15658210 ] Hudson commented on MNG-6112: - FAILURE: Integrated in Jenkins build maven-3.x Jigsaw #5 (See [h

[jira] [Commented] (MNG-6113) Rename the 'Central Repository' to 'Maven Central Repository' in the 4.0.0 super POM.

[ https://issues.apache.org/jira/browse/MNG-6113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15658207#comment-15658207 ] Hudson commented on MNG-6113: - FAILURE: Integrated in Jenkins build maven-3.x Jigsaw #5 (See [h

[jira] [Commented] (MNG-6113) Rename the 'Central Repository' to 'Maven Central Repository' in the 4.0.0 super POM.

[ https://issues.apache.org/jira/browse/MNG-6113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15658219#comment-15658219 ] Hudson commented on MNG-6113: - SUCCESS: Integrated in Jenkins build maven-3.x #1406 (See [https

[jira] [Commented] (MNG-6112) Central repository in the 4.0.0 super POM should declare update policy 'never'.

[ https://issues.apache.org/jira/browse/MNG-6112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15658220#comment-15658220 ] Hudson commented on MNG-6112: - SUCCESS: Integrated in Jenkins build maven-3.x #1406 (See [https

[jira] [Commented] (MDEPLOY-211) uniqueVersion broken (if not supported, should be removed from doc, and warning printed)

[ https://issues.apache.org/jira/browse/MDEPLOY-211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15658221#comment-15658221 ] Hudson commented on MDEPLOY-211: SUCCESS: Integrated in Jenkins build maven-plugins #7598

[jira] [Closed] (MDEPLOY-211) uniqueVersion broken (if not supported, should be removed from doc, and warning printed)

[ https://issues.apache.org/jira/browse/MDEPLOY-211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Boué closed MDEPLOY-211. -- Resolution: Fixed Assignee: Guillaume Boué Fix Version/s: 3.0.0 > uniqueVersion

[jira] [Commented] (SUREFIRE-1300) threadCount is 0 when surefire-junit47 and surefire-testng are used together

[ https://issues.apache.org/jira/browse/SUREFIRE-1300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15658249#comment-15658249 ] Tibor Digana commented on SUREFIRE-1300: [~juherr] Why TestNG needs to have Sur

[jira] [Updated] (MNG-6070) Default profile in settings.xml must not use an id possibly already in use.

[ https://issues.apache.org/jira/browse/MNG-6070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schulte updated MNG-6070: --- Fix Version/s: (was: 3.4.0) > Default profile in settings.xml must not use an id possibly al

[jira] [Reopened] (MNG-6070) Default profile in settings.xml must not use an id possibly already in use.

[ https://issues.apache.org/jira/browse/MNG-6070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schulte reopened MNG-6070: Assignee: (was: Christian Schulte) > Default profile in settings.xml must not use an id

[jira] [Closed] (MNG-6070) Default profile in settings.xml must not use an id possibly already in use.

[ https://issues.apache.org/jira/browse/MNG-6070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schulte closed MNG-6070. -- Resolution: Not A Problem Assignee: Christian Schulte This was caused when the central repos

[jira] [Updated] (MNG-6070) Default profile in settings.xml must not use an id possibly already in use.

[ https://issues.apache.org/jira/browse/MNG-6070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schulte updated MNG-6070: --- Assignee: (was: Christian Schulte) > Default profile in settings.xml must not use an id poss

[jira] [Commented] (MRELEASE-827) Passing "-pl" via arguments is not accepted

[ https://issues.apache.org/jira/browse/MRELEASE-827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15658404#comment-15658404 ] Dmitriy Mikhelson commented on MRELEASE-827: I'm having the same problem. I'

[jira] [Commented] (MNG-6112) Central repository in the 4.0.0 super POM should declare update policy 'never'.

[ https://issues.apache.org/jira/browse/MNG-6112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15658451#comment-15658451 ] Hudson commented on MNG-6112: - FAILURE: Integrated in Jenkins build maven-3.x Jigsaw #6 (See [h

[jira] [Commented] (MNG-6112) Central repository in the 4.0.0 super POM should declare update policy 'never'.

[ https://issues.apache.org/jira/browse/MNG-6112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15658461#comment-15658461 ] Hudson commented on MNG-6112: - SUCCESS: Integrated in Jenkins build maven-3.x #1407 (See [https

[jira] [Commented] (SUREFIRE-1300) threadCount is 0 when surefire-junit47 and surefire-testng are used together

[ https://issues.apache.org/jira/browse/SUREFIRE-1300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15659098#comment-15659098 ] Julien Herr commented on SUREFIRE-1300: --- I don't know but it is the default behav