[jira] [Comment Edited] (MNG-5964) Corrupt artifact from stale repository makes build fail, even though correct artifact is available

[ https://issues.apache.org/jira/browse/MNG-5964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15110159#comment-15110159 ] Hendy Irawan edited comment on MNG-5964 at 1/22/16 9:53 AM: Workaround is to put

[jira] [Comment Edited] (MNG-5964) Corrupt artifact from stale repository makes build fail, even though correct artifact is available

[ https://issues.apache.org/jira/browse/MNG-5964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15110159#comment-15110159 ] Hendy Irawan edited comment on MNG-5964 at 1/22/16 6:19 AM: Workaround is to put

[jira] [Created] (MNG-5964) Corrupt artifact from stale repository makes build fail, even though correct artifact is available

Hendy Irawan created MNG-5964: - Summary: Corrupt artifact from stale repository makes build fail, even though correct artifact is available Key: MNG-5964 URL: https://issues.apache.org/jira/browse/MNG-5964

[jira] [Commented] (MNG-5964) Corrupt artifact from stale repository makes build fail, even though correct artifact is available

[ https://issues.apache.org/jira/browse/MNG-5964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15110159#comment-15110159 ] Hendy Irawan commented on MNG-5964: --- Workaround is to put this in {{~/.m2.settings.xml}} : {code}

[jira] [Comment Edited] (MNG-5964) Corrupt artifact from stale repository makes build fail, even though correct artifact is available

[ https://issues.apache.org/jira/browse/MNG-5964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15110159#comment-15110159 ] Hendy Irawan edited comment on MNG-5964 at 1/21/16 6:38 AM: Workaround is to put

[jira] (MWAR-340) packagingExcludes is ignored by war:exploded

[ https://jira.codehaus.org/browse/MWAR-340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hendy Irawan updated MWAR-340: -- Affects Version/s: 2.6 packagingExcludes is ignored by war:exploded

[jira] (MWAR-340) packagingExcludes is ignored by war:exploded

[ https://jira.codehaus.org/browse/MWAR-340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=365057#comment-365057 ] Hendy Irawan commented on MWAR-340: --- Please take a look at this issue. Still happens on 2.6 :(

[jira] (MJAVADOC-387) Handle JDK8 -Xdoclint

[ https://jira.codehaus.org/browse/MJAVADOC-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=360788#comment-360788 ] Hendy Irawan commented on MJAVADOC-387: --- {{doclint}} should be a configuration option in

[jira] (MWAR-340) packagingExcludes is ignored by war:exploded

Hendy Irawan created MWAR-340: - Summary: packagingExcludes is ignored by war:exploded Key: MWAR-340 URL: https://jira.codehaus.org/browse/MWAR-340 Project: Maven WAR Plugin Issue Type: Bug

[jira] (MNG-5363) Regression for SSLv3

[ https://jira.codehaus.org/browse/MNG-5363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=316181#comment-316181 ] Hendy Irawan commented on MNG-5363: --- +1... Regression for SSLv3

[jira] (MNG-1012) parent with only relativePath doesn't work

[ https://jira.codehaus.org/browse/MNG-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=312329#comment-312329 ] Hendy Irawan commented on MNG-1012: --- I agree with David. As it stands now, it's pretty annoying

[jira] (MNG-1012) parent with only relativePath doesn't work

[ https://jira.codehaus.org/browse/MNG-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=312329#comment-312329 ] Hendy Irawan edited comment on MNG-1012 at 10/25/12 4:29 PM: - I agree

[jira] (MNG-2258) Wrong execution order of plugins in same phase

[ https://jira.codehaus.org/browse/MNG-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=304874#comment-304874 ] Hendy Irawan commented on MNG-2258: --- Thank you Barrie. I tried to reproduce the problem but it

[jira] (MNG-2258) Wrong execution order of plugins in same phase

[ https://jira.codehaus.org/browse/MNG-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=304856#comment-304856 ] Hendy Irawan commented on MNG-2258: --- This bug isn't fixed yet. I'm using Maven 3.0.4 and the

[jira] Created: (MSOURCES-58) Maven Source Plugin does not work if project packaging=bundle (OSGi Bundle)

Maven Source Plugin does not work if project packaging=bundle (OSGi Bundle) --- Key: MSOURCES-58 URL: https://jira.codehaus.org/browse/MSOURCES-58 Project: Maven 2.x Source

[jira] Commented: (MWAR-187) regression running war packaging with maven 2.1

[ http://jira.codehaus.org/browse/MWAR-187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=181418#action_181418 ] Hendy Irawan commented on MWAR-187: --- Using 2.1-alpha-1 although solved the problem, it still occurs

[jira] Commented: (MWAR-187) regression running war packaging with maven 2.1

[ http://jira.codehaus.org/browse/MWAR-187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=177311#action_177311 ] Hendy Irawan commented on MWAR-187: --- Downgrading to war-plugin 2.0.2 didn't solve the problem for me,

[jira] Commented: (WAGON-84) exception deploying with webdav

[ http://jira.codehaus.org/browse/WAGON-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=176899#action_176899 ] Hendy Irawan commented on WAGON-84: --- wagon-webdav is now (name changed) wagon-webdav-jackrabbit I'm