[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=16101118#comment-16101118 ] Hudson commented on SUREFIRE-1302: -- SUCCESS: Integrated in Jenkins build maven-surefir

[jira] [Commented] (SUREFIRE-1383) dependenciesToScan Does Not Leverage Classpath Elements

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

[jira] [Commented] (SUREFIRE-1383) dependenciesToScan Does Not Leverage Classpath Elements

[ https://issues.apache.org/jira/browse/SUREFIRE-1383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16101085#comment-16101085 ] ASF GitHub Bot commented on SUREFIRE-1383: -- GitHub user owenfarrell reopened a

[jira] [Commented] (SUREFIRE-1383) dependenciesToScan Does Not Leverage Classpath Elements

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

[jira] [Commented] (SUREFIRE-1383) dependenciesToScan Does Not Leverage Classpath Elements

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

[jira] [Updated] (MJAVADOC-420) javadoc:fix duplicates lines

[ https://issues.apache.org/jira/browse/MJAVADOC-420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MJAVADOC-420: Description: On the following example, if you starts several times the javadoc:fix goal, t

[jira] [Commented] (SUREFIRE-1398) TestNG test fails when both JUnitCore provider and TestNG provider are on classpath

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

[jira] [Commented] (SUREFIRE-1398) TestNG test fails when both JUnitCore provider and TestNG provider are on classpath

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

[jira] [Commented] (SUREFIRE-1398) TestNG test fails when both JUnitCore provider and TestNG provider are on classpath

[ https://issues.apache.org/jira/browse/SUREFIRE-1398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16100105#comment-16100105 ] Matous Jobanek commented on SUREFIRE-1398: -- Pull request: https://github.com/a

[jira] [Issue Comment Deleted] (SUREFIRE-1398) TestNG test fails when both JUnitCore provider and TestNG provider are on classpath

[ https://issues.apache.org/jira/browse/SUREFIRE-1398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matous Jobanek updated SUREFIRE-1398: - Comment: was deleted (was: Pull request: https://github.com/apache/maven-surefire/pull/

[jira] [Commented] (SUREFIRE-1398) TestNG test fails when both JUnitCore provider and TestNG provider are on classpath

[ https://issues.apache.org/jira/browse/SUREFIRE-1398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16100103#comment-16100103 ] ASF GitHub Bot commented on SUREFIRE-1398: -- GitHub user MatousJobanek opened a

[jira] [Created] (SUREFIRE-1398) TestNG test fails when both JUnitCore provider and TestNG provider are on classpath

Matous Jobanek created SUREFIRE-1398: Summary: TestNG test fails when both JUnitCore provider and TestNG provider are on classpath Key: SUREFIRE-1398 URL: https://issues.apache.org/jira/browse/SUREFIRE-1398

[jira] [Updated] (SUREFIRE-1397) "ExecutionException Cannot create workingDirectory" occurs randomly when forkCount>1

[ https://issues.apache.org/jira/browse/SUREFIRE-1397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Krokowski updated SUREFIRE-1397: -- Description: I've verified the same scenario with 2.18, 2.19 and 2.20 versions of the

[jira] [Updated] (SUREFIRE-1397) "ExecutionException Cannot create workingDirectory" occurs randomly when forkCount>1

[ https://issues.apache.org/jira/browse/SUREFIRE-1397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Krokowski updated SUREFIRE-1397: -- Description: I've verified the same scenario with 2.18, 2.19 and 2.20 versions of the

[jira] [Updated] (SUREFIRE-1397) "ExecutionException Cannot create workingDirectory" occurs randomly when forkCount>1

[ https://issues.apache.org/jira/browse/SUREFIRE-1397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Krokowski updated SUREFIRE-1397: -- Description: I've verified the same scenario with 2.18, 2.19 and 2.20 versions of the

[jira] [Comment Edited] (SUREFIRE-1397) "ExecutionException Cannot create workingDirectory" occurs randomly when forkCount>1

[ https://issues.apache.org/jira/browse/SUREFIRE-1397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16100022#comment-16100022 ] Piotr Krokowski edited comment on SUREFIRE-1397 at 7/25/17 1:24 PM: -

[jira] [Comment Edited] (SUREFIRE-1397) "ExecutionException Cannot create workingDirectory" occurs randomly when forkCount>1

[ https://issues.apache.org/jira/browse/SUREFIRE-1397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16100022#comment-16100022 ] Piotr Krokowski edited comment on SUREFIRE-1397 at 7/25/17 1:24 PM: -

[jira] [Commented] (SUREFIRE-1397) "ExecutionException Cannot create workingDirectory" occurs randomly when forkCount>1

[ https://issues.apache.org/jira/browse/SUREFIRE-1397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16100022#comment-16100022 ] Piotr Krokowski commented on SUREFIRE-1397: --- I've found out that using: ${te

[jira] [Updated] (SUREFIRE-1397) "ExecutionException Cannot create workingDirectory" occurs randomly when forkCount>1

[ https://issues.apache.org/jira/browse/SUREFIRE-1397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Krokowski updated SUREFIRE-1397: -- Description: I've verified the same scenario with 2.18, 2.19 and 2.20 versions of the

[jira] [Updated] (SUREFIRE-1397) "ExecutionException Cannot create workingDirectory" occurs randomly when forkCount>1

[ https://issues.apache.org/jira/browse/SUREFIRE-1397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Krokowski updated SUREFIRE-1397: -- Summary: "ExecutionException Cannot create workingDirectory" occurs randomly when for

[jira] [Created] (SUREFIRE-1397) ExecutionException Cannot create workingDirectory randomly occurs when forkCount>1

Piotr Krokowski created SUREFIRE-1397: - Summary: ExecutionException Cannot create workingDirectory randomly occurs when forkCount>1 Key: SUREFIRE-1397 URL: https://issues.apache.org/jira/browse/SUREFIRE-1397

[jira] [Updated] (MASSEMBLY-865) dependencySet "include" seems to implicitly append wildcards to simple groupId:artifactId values

[ https://issues.apache.org/jira/browse/MASSEMBLY-865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yoann Rodière updated MASSEMBLY-865: Attachment: integration-test.patch Description: When a multi-module project has the

[jira] [Updated] (MASSEMBLY-865) dependencySet "include" seems to implicitly append wildcards to simple groupId:artifactId values

[ https://issues.apache.org/jira/browse/MASSEMBLY-865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yoann Rodière updated MASSEMBLY-865: Description: When a multi-module project has the following modules: * prefix * prefix-su

[jira] [Created] (MASSEMBLY-865) dependencySet "include" seems to implicitly append wildcards to simple groupId:artifactId values

Yoann Rodière created MASSEMBLY-865: --- Summary: dependencySet "include" seems to implicitly append wildcards to simple groupId:artifactId values Key: MASSEMBLY-865 URL: https://issues.apache.org/jira/browse/MASSE