[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&focusedCommentId=15110159#comment-15110159 ] Hendy Irawan edited comment on MNG-5964 at 1/21/16 6:38 AM: Work

[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&focusedCommentId=15110159#comment-15110159 ] Hendy Irawan commented on MNG-5964: --- Workaround is to put this in {{~/.m2.settings.xml}} :

[jira] [Updated] (SUREFIRE-1219) skipAfterFailureCount should not count flaky tests as failures when using rerunFailingTestsCount

[ https://issues.apache.org/jira/browse/SUREFIRE-1219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Flanigan updated SUREFIRE-1219: Attachment: SUREFIRE-1219-tests.zip Integration tests for SUREFIRE-1219. > skipAfterFail

[jira] [Created] (SUREFIRE-1219) skipAfterFailureCount should not count flaky tests as failures when using rerunFailingTestsCount

Sean Flanigan created SUREFIRE-1219: --- Summary: skipAfterFailureCount should not count flaky tests as failures when using rerunFailingTestsCount Key: SUREFIRE-1219 URL: https://issues.apache.org/jira/browse/SUREF

[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] (MJAVADOC-387) Handle JDK8 -Xdoclint

[ https://issues.apache.org/jira/browse/MJAVADOC-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15109788#comment-15109788 ] Sergei Ivanov commented on MJAVADOC-387: If the above behaviour is going to be d

[jira] [Updated] (SCM-815) maven-scm-provider-gitexe 1.9.x doesn't commit files any more under Cygwin (and other bash variants)

[ https://issues.apache.org/jira/browse/SCM-815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Galsterer updated SCM-815: Description: In https://github.com/apache/maven-scm/blob/maven-scm-1.9.1/maven-scm-providers/m

[jira] [Comment Edited] (SCM-791) maven-scm-provider-gitexe - Lastest version (1.9.2) doesn't work properly in Cygwin

[ https://issues.apache.org/jira/browse/SCM-791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15108945#comment-15108945 ] Christian Galsterer edited comment on SCM-791 at 1/20/16 5:19 PM: -

[jira] [Updated] (SCM-815) maven-scm-provider-gitexe 1.9.x doesn't commit files any more under Cygwin (and other bash variants)

[ https://issues.apache.org/jira/browse/SCM-815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Galsterer updated SCM-815: Environment: Cygwin and other bash variants > maven-scm-provider-gitexe 1.9.x doesn't commit fi

[jira] [Created] (SCM-815) maven-scm-provider-gitexe 1.9.x doesn't commit files any more under Cygwin (and other bash variants)

Christian Galsterer created SCM-815: --- Summary: maven-scm-provider-gitexe 1.9.x doesn't commit files any more under Cygwin (and other bash variants) Key: SCM-815 URL: https://issues.apache.org/jira/browse/SCM-815

[jira] [Commented] (SCM-791) maven-scm-provider-gitexe - Lastest version (1.9.2) doesn't work properly in Cygwin

[ https://issues.apache.org/jira/browse/SCM-791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15108945#comment-15108945 ] Christian Galsterer commented on SCM-791: - I think the problem was introduced in 1.9.

[jira] [Updated] (MRELEASE-939) release:perform uses incorrect ReleaseDescriptor.scmRelativePathProjectDirectory in nested multi-module project

[ https://issues.apache.org/jira/browse/MRELEASE-939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jürgen updated MRELEASE-939: Description: I recently migrated from svn to git I have the same issues as described in MRELEASE-927. I u

[jira] [Updated] (MRELEASE-939) release:perform uses incorrect ReleaseDescriptor.scmRelativePathProjectDirectory in nested multi-module project

[ https://issues.apache.org/jira/browse/MRELEASE-939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jürgen updated MRELEASE-939: Description: I recently migrated from svn to git I have the same issues as described in MRELEASE-927. I u

[jira] [Updated] (MRELEASE-939) release:perform uses incorrect ReleaseDescriptor.scmRelativePathProjectDirectory in nested multi-module project

[ https://issues.apache.org/jira/browse/MRELEASE-939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jürgen updated MRELEASE-939: Attachment: GitperformReleaseMojo.java > release:perform uses incorrect > ReleaseDescriptor.scmRelativePa

[jira] [Updated] (MRELEASE-939) release:perform uses incorrect ReleaseDescriptor.scmRelativePathProjectDirectory in nested multi-module project

[ https://issues.apache.org/jira/browse/MRELEASE-939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jürgen updated MRELEASE-939: Description: I recently migrated from svn to git I have the same issues as described in MRELEASE-927. I u

[jira] [Updated] (MRELEASE-939) release:perform uses incorrect ReleaseDescriptor.scmRelativePathProjectDirectory in nested multi-module project

[ https://issues.apache.org/jira/browse/MRELEASE-939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jürgen updated MRELEASE-939: Description: I recently migrated from svn to git I have the same issues as described in MRELEASE-927. I u

[jira] [Updated] (MRELEASE-939) release:perform uses incorrect ReleaseDescriptor.scmRelativePathProjectDirectory in nested multi-module project

[ https://issues.apache.org/jira/browse/MRELEASE-939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jürgen updated MRELEASE-939: Description: I recently migrated from svn to git I have the same issues as described in MRELEASE-927. I u

[jira] [Created] (MRELEASE-939) release:perform uses incorrect ReleaseDescriptor.scmRelativePathProjectDirectory in nested multi-module project

Jürgen created MRELEASE-939: --- Summary: release:perform uses incorrect ReleaseDescriptor.scmRelativePathProjectDirectory in nested multi-module project Key: MRELEASE-939 URL: https://issues.apache.org/jira/browse/MRELEAS

[jira] [Commented] (DOXIA-539) language element of code block is ignored

[ https://issues.apache.org/jira/browse/DOXIA-539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15108585#comment-15108585 ] Robin Roos commented on DOXIA-539: -- Sorry this issue is so thin on details. I will update

[jira] [Created] (DOXIA-539) language element of code block is ignored

Robin Roos created DOXIA-539: Summary: language element of code block is ignored Key: DOXIA-539 URL: https://issues.apache.org/jira/browse/DOXIA-539 Project: Maven Doxia Issue Type: Bug

[jira] [Commented] (MRESOURCES-212) maven resource plugin does not preserve symlinks

[ https://issues.apache.org/jira/browse/MRESOURCES-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15108276#comment-15108276 ] Michael Osipov commented on MRESOURCES-212: --- There are at least two ways to