[jira] [Created] (MNG-6120) Allow changing of default scope and change the default scope

2016-11-15 Thread Caleb Cushing (JIRA)
Caleb Cushing created MNG-6120: -- Summary: Allow changing of default scope and change the default scope Key: MNG-6120 URL: https://issues.apache.org/jira/browse/MNG-6120 Project: Maven Issue Typ

[jira] [Commented] (MJAVADOC-311) Aggregated javadoc report not generated for multi-module project at sub-level if run from parent level.

2016-11-15 Thread Taylor Jones (JIRA)
[ https://issues.apache.org/jira/browse/MJAVADOC-311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668421#comment-15668421 ] Taylor Jones commented on MJAVADOC-311: --- I've also hit this issue. Can one of the

[jira] [Commented] (MNG-6119) Artifact has bad name

2016-11-15 Thread James youngman (JIRA)
[ https://issues.apache.org/jira/browse/MNG-6119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15667935#comment-15667935 ] James youngman commented on MNG-6119: - Thanks for the info. I see this bug has been ope

[jira] [Commented] (MNG-6119) Artifact has bad name

2016-11-15 Thread JIRA
[ https://issues.apache.org/jira/browse/MNG-6119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15667863#comment-15667863 ] Guillaume Boué commented on MNG-6119: - {{checksum-maven-plugin}} is good for this. I als

[jira] [Comment Edited] (MNG-6119) Artifact has bad name

2016-11-15 Thread JIRA
[ https://issues.apache.org/jira/browse/MNG-6119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15667863#comment-15667863 ] Guillaume Boué edited comment on MNG-6119 at 11/15/16 6:21 PM: ---

[jira] [Commented] (MNG-6119) Artifact has bad name

2016-11-15 Thread James youngman (JIRA)
[ https://issues.apache.org/jira/browse/MNG-6119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15667799#comment-15667799 ] James youngman commented on MNG-6119: - OK. I do see the checksums in the cache now. Un

[jira] [Commented] (MNG-6119) Artifact has bad name

2016-11-15 Thread JIRA
[ https://issues.apache.org/jira/browse/MNG-6119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15667766#comment-15667766 ] Guillaume Boué commented on MNG-6119: - Yes, it's normal not to have the checksum file in

[jira] [Commented] (MNG-6119) Artifact has bad name

2016-11-15 Thread James youngman (JIRA)
[ https://issues.apache.org/jira/browse/MNG-6119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15667744#comment-15667744 ] James youngman commented on MNG-6119: - I made the change exactly as you specified below

[jira] [Closed] (MNG-6119) Artifact has bad name

2016-11-15 Thread JIRA
[ https://issues.apache.org/jira/browse/MNG-6119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Boué closed MNG-6119. --- Resolution: Not A Problem > Artifact has bad name > - > > Key: MNG-6

[jira] [Commented] (MNG-6119) Artifact has bad name

2016-11-15 Thread JIRA
[ https://issues.apache.org/jira/browse/MNG-6119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15667673#comment-15667673 ] Guillaume Boué commented on MNG-6119: - This is not a bug in Maven, but in the {{checksum

[jira] [Created] (SUREFIRE-1304) VM crash when using reportsDirectory pointing to parent module and maven parallel build

2016-11-15 Thread JIRA
Jérôme Van Der Linden created SUREFIRE-1304: --- Summary: VM crash when using reportsDirectory pointing to parent module and maven parallel build Key: SUREFIRE-1304 URL: https://issues.apache.org/jira/brows

[jira] [Commented] (MNG-6119) Artifact has bad name

2016-11-15 Thread James youngman (JIRA)
[ https://issues.apache.org/jira/browse/MNG-6119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15667565#comment-15667565 ] James youngman commented on MNG-6119: - Sorry about that. I have attached it directly to

[jira] [Updated] (MNG-6119) Artifact has bad name

2016-11-15 Thread James youngman (JIRA)
[ https://issues.apache.org/jira/browse/MNG-6119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James youngman updated MNG-6119: Attachment: commons-jelly-2.0-src.zip > Artifact has bad name > - > >

[jira] [Commented] (MNG-6119) Artifact has bad name

2016-11-15 Thread JIRA
[ https://issues.apache.org/jira/browse/MNG-6119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15667543#comment-15667543 ] Guillaume Boué commented on MNG-6119: - It looks like there was an issue while uploading

[jira] [Updated] (MNG-6119) Artifact has bad name

2016-11-15 Thread James youngman (JIRA)
[ https://issues.apache.org/jira/browse/MNG-6119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James youngman updated MNG-6119: Attachment: commons-jelly-2.0-src.zip.txt I have attached a zip of the source project. > Artifact h

[jira] [Closed] (WAGON-460) Upgrade plexus-utils to 3.0.24

2016-11-15 Thread Michael Osipov (JIRA)
[ https://issues.apache.org/jira/browse/WAGON-460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed WAGON-460. Resolution: Fixed > Upgrade plexus-utils to 3.0.24 > -- > >

[jira] [Commented] (MDEPLOY-177) Maven release:perform hangs when downloading maven-metadata.xml

2016-11-15 Thread Martin Charlesworth (JIRA)
[ https://issues.apache.org/jira/browse/MDEPLOY-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15666909#comment-15666909 ] Martin Charlesworth commented on MDEPLOY-177: - FWIW I suffered from this issu

[jira] [Created] (MWAR-399) Maven WAR Plugin imports MAR/AAR Dependencies - can not be disabled

2016-11-15 Thread Jeff Thomas (JIRA)
Jeff Thomas created MWAR-399: Summary: Maven WAR Plugin imports MAR/AAR Dependencies - can not be disabled Key: MWAR-399 URL: https://issues.apache.org/jira/browse/MWAR-399 Project: Maven WAR Plugin

[jira] [Commented] (MNG-5889) .mvn directory should be picked when using --file

2016-11-15 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/MNG-5889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15666720#comment-15666720 ] ASF GitHub Bot commented on MNG-5889: - Github user hboutemy commented on the issue:

[jira] [Closed] (MNG-5889) .mvn directory should be picked when using --file

2016-11-15 Thread JIRA
[ https://issues.apache.org/jira/browse/MNG-5889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy closed MNG-5889. -- Resolution: Fixed > .mvn directory should be picked when using --file > --

[jira] [Commented] (MNG-5889) .mvn directory should be picked when using --file

2016-11-15 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/MNG-5889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15666523#comment-15666523 ] ASF GitHub Bot commented on MNG-5889: - Github user michael-o commented on the issue:

[jira] [Commented] (SUREFIRE-1216) TEST-*.xml files generated by Surefire are invalid

2016-11-15 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/SUREFIRE-1216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15666471#comment-15666471 ] ASF GitHub Bot commented on SUREFIRE-1216: -- Github user stdweird commented on