[jira] [Commented] (MNG-6262) getCanonicalFile() is not used consistently during project resolution

[ https://issues.apache.org/jira/browse/MNG-6262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16109623#comment-16109623 ] Robert Scholte commented on MNG-6262: - Maven now requires Java 7, so this is probably a good reason to

[jira] [Closed] (MNG-6266) Getting error " 2.6 or one of its dependencies could not be resolved" while creating a project in Eclipse.

[ https://issues.apache.org/jira/browse/MNG-6266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MNG-6266. --- Resolution: Not A Problem Assignee: Robert Scholte Closing it for now, just reopen if you have

[jira] [Updated] (MSHADE-257) Bad zero length source jars published by 3rd parties cause source jar creation to fail.

[ https://issues.apache.org/jira/browse/MSHADE-257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jess updated MSHADE-257: Attachment: maven-shade-plugin-257-patch.diff Simple guard against zero length source jars. > Bad zero length

[jira] [Created] (MSHADE-257) Bad zero length source jars published by 3rd parties cause source jar creation to fail.

Jess created MSHADE-257: --- Summary: Bad zero length source jars published by 3rd parties cause source jar creation to fail. Key: MSHADE-257 URL: https://issues.apache.org/jira/browse/MSHADE-257 Project: Maven

[jira] [Updated] (MSHADE-254) NullPointerException thrown by Maven Shade Plugin 3.0.0

[ https://issues.apache.org/jira/browse/MSHADE-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jess updated MSHADE-254: Attachment: maven-shade-plugin-254-patch.diff The attached patch adds a guard to handle the null return behavior

[jira] [Commented] (MNG-6265) Controlling reactor order of modules

[ https://issues.apache.org/jira/browse/MNG-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16109351#comment-16109351 ] August Shi commented on MNG-6265: - Thank you for pointing out the --builder option. We implemented a custom

[jira] [Commented] (MRELEASE-911) release plugin forming incorrect git clone command

[ https://issues.apache.org/jira/browse/MRELEASE-911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16109293#comment-16109293 ] Robert Scholte commented on MRELEASE-911: - [~inforedaster] have you read

[jira] [Created] (MPLUGINTESTING-53) default-value on mojo parameter of type collection or array effectively make parameter read-only

Konrad Windszus created MPLUGINTESTING-53: - Summary: default-value on mojo parameter of type collection or array effectively make parameter read-only Key: MPLUGINTESTING-53 URL:

[jira] [Commented] (SUREFIRE-1396) Provider class path is incorrect for custom provider in Failsafe

[ https://issues.apache.org/jira/browse/SUREFIRE-1396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16108791#comment-16108791 ] ASF GitHub Bot commented on SUREFIRE-1396: -- Github user jon-bell commented on the issue:

[jira] [Commented] (MRELEASE-911) release plugin forming incorrect git clone command

[ https://issues.apache.org/jira/browse/MRELEASE-911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16108570#comment-16108570 ] Med Reda commented on MRELEASE-911: --- release:prepare + release:perform ==> create a tag has version

[jira] [Commented] (SUREFIRE-1396) Provider class path is incorrect for custom provider in Failsafe

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

[jira] [Commented] (SUREFIRE-1400) Windows surefire boot directory should appear in system default temporary-directory

[ https://issues.apache.org/jira/browse/SUREFIRE-1400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16108527#comment-16108527 ] Tibor Digana commented on SUREFIRE-1400: [~gboue] [~tunaki] I could not establish IT because

[jira] [Updated] (SUREFIRE-1400) Windows surefire boot directory should appear in system default temporary-directory

[ https://issues.apache.org/jira/browse/SUREFIRE-1400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-1400: --- Description: Windows paths are limited in length. The path of surefire boot should point

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

[ https://issues.apache.org/jira/browse/SUREFIRE-1376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16108523#comment-16108523 ] Tibor Digana commented on SUREFIRE-1376: [~gboue] [~tunaki] I have created Jira ticket

[jira] [Commented] (SUREFIRE-1400) Windows surefire boot directory should appear in system default temporary-directory

[ https://issues.apache.org/jira/browse/SUREFIRE-1400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16108524#comment-16108524 ] Tibor Digana commented on SUREFIRE-1400: Review ASF branch

[jira] [Issue Comment Deleted] (MRELEASE-911) release plugin forming incorrect git clone command

[ https://issues.apache.org/jira/browse/MRELEASE-911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Med Reda updated MRELEASE-911: -- Comment: was deleted (was: When i use release:prepare with release:perform it works fin and it

[jira] [Created] (SUREFIRE-1400) Windows surefire boot directory should appear in system default temporary-directory

Tibor Digana created SUREFIRE-1400: -- Summary: Windows surefire boot directory should appear in system default temporary-directory Key: SUREFIRE-1400 URL: https://issues.apache.org/jira/browse/SUREFIRE-1400