[jira] [Created] (MNG-6583) Relative path for parent pom on Windows fails depending on case of drive letter

J.Cranendonk created MNG-6583: - Summary: Relative path for parent pom on Windows fails depending on case of drive letter Key: MNG-6583 URL: https://issues.apache.org/jira/browse/MNG-6583 Project: Maven

[jira] [Updated] (MNG-6583) Relative path for parent pom on Windows fails depending on case of drive letter

[ https://issues.apache.org/jira/browse/MNG-6583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] J.Cranendonk updated MNG-6583: -- Description: Hi! I've found an odd issue with Maven 3.5.0 and higher (including current: 3.6.0) This

[jira] [Updated] (MNG-6583) Relative path for parent pom on Windows fails depending on case of drive letter

[ https://issues.apache.org/jira/browse/MNG-6583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] J.Cranendonk updated MNG-6583: -- Description: Hi! I've found an odd issue with Maven 3.5.0 and higher (including current: 3.6.0) This

[jira] [Updated] (MNG-6583) Relative path for parent pom on Windows fails depending on case of drive letter

[ https://issues.apache.org/jira/browse/MNG-6583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] J.Cranendonk updated MNG-6583: -- Attachment: RelativelyInsane.7z > Relative path for parent pom on Windows fails depending on case of

[jira] [Updated] (MNG-6583) Relative path for parent pom on Windows fails depending on case of drive letter

[ https://issues.apache.org/jira/browse/MNG-6583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] J.Cranendonk updated MNG-6583: -- Description: Hi! I've found an odd issue with Maven 3.5.0 and higher (including current: 3.6.0) This

[jira] [Commented] (MJAR-253) Since 3.0.0 builds fail with You have to use a classifier to attach supplemental artifacts to the project instead of replacing them.

[ https://issues.apache.org/jira/browse/MJAR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517880#comment-16517880 ] J.Cranendonk commented on MJAR-253: --- Wrong is a big word, but uncommon possibly :) The artifact is a zip

[jira] [Created] (MJAR-253) Since 3.0.0 builds fail with You have to use a classifier to attach supplemental artifacts to the project instead of replacing them.

J.Cranendonk created MJAR-253: - Summary: Since 3.0.0 builds fail with You have to use a classifier to attach supplemental artifacts to the project instead of replacing them. Key: MJAR-253 URL:

[jira] [Commented] (MJAR-198) jar:jar without classifier replaces default jar

[ https://issues.apache.org/jira/browse/MJAR-198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16516772#comment-16516772 ] J.Cranendonk commented on MJAR-198: --- Was an issue made for the comment Archie Cobbs mentioned? We have

[jira] [Created] (SUREFIRE-1466) Surefire fails on a dummy:dummy dependency with a authenticating proxy

J.Cranendonk created SUREFIRE-1466: -- Summary: Surefire fails on a dummy:dummy dependency with a authenticating proxy Key: SUREFIRE-1466 URL: https://issues.apache.org/jira/browse/SUREFIRE-1466