[
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 issue does not appear in Maven 3.3.9 or older.
Works: 3.3.3, 3.3.9
Fails: 3.5.0, 3.5.2, 3.5.3, 3.5.4, 3.6.0
It seems to be related to whether the cmd current path either starts with a
upper case (works) or lower case (doesn't work) driver letter.
With an upper case drive letter, relative paths to the parent pom resolve
correctly.
With a lower case driver letter, relative paths to the parent pom do not
resolve correctly.
For example, this cmd works:
{{@ECHO OFF}}
{{SET M2_HOME=C:\Portable\Tools\apache-maven-3.6.0}}
{{SET PATH=%M2_HOME%\bin;%PATH%}}
{{cd ..}}
{{cd *+C+*:\Temp\RelativelyInsane}}
{{call mvn clean}}
{{call mvn -vesion}}
{{pause}}
And this cmd fails, the only difference is the drive letter in the second 'cd'.
{{@ECHO OFF}}
{{SET M2_HOME=C:\Portable\Tools\apache-maven-3.6.0}}
{{SET PATH=%M2_HOME%\bin;%PATH%}}
{{cd ..}}
{{cd *+c+*:\Temp\RelativelyInsane}}
{{call mvn clean}}
{{call mvn -vesion}}
{{pause}}
was:
Hi! I've found an odd issue with Maven 3.5.0 and higher (including current:
3.6.0)
This issue does not appear in Maven 3.3.9 or older.
Works: 3.3.3, 3.3.9
Fails: 3.5.0, 3.5.2, 3.5.3, 3.5.4, 3.6.0
It seems to be related to whether the cmd current path either starts with a
upper case (works) or lower case (doesn't work) driver letter.
With an upper case drive letter, relative paths to the parent pom resolve
correctly.
With a lower case driver letter, relative paths to the parent pom do not
resolve correctly.
(I will add a sample after creating the issue)
> 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
> Issue Type: Bug
> Components: POM
> Affects Versions: 3.5.0, 3.5.2, 3.5.3, 3.5.4, 3.6.0
> Environment: Windows 7 Enterprise
> Reporter: J.Cranendonk
> Priority: Major
> Attachments: RelativelyInsane.7z
>
>
> Hi! I've found an odd issue with Maven 3.5.0 and higher (including current:
> 3.6.0)
> This issue does not appear in Maven 3.3.9 or older.
> Works: 3.3.3, 3.3.9
> Fails: 3.5.0, 3.5.2, 3.5.3, 3.5.4, 3.6.0
> It seems to be related to whether the cmd current path either starts with a
> upper case (works) or lower case (doesn't work) driver letter.
> With an upper case drive letter, relative paths to the parent pom resolve
> correctly.
> With a lower case driver letter, relative paths to the parent pom do not
> resolve correctly.
> For example, this cmd works:
> {{@ECHO OFF}}
> {{SET M2_HOME=C:\Portable\Tools\apache-maven-3.6.0}}
> {{SET PATH=%M2_HOME%\bin;%PATH%}}
> {{cd ..}}
> {{cd *+C+*:\Temp\RelativelyInsane}}
> {{call mvn clean}}
> {{call mvn -vesion}}
> {{pause}}
> And this cmd fails, the only difference is the drive letter in the second
> 'cd'.
> {{@ECHO OFF}}
> {{SET M2_HOME=C:\Portable\Tools\apache-maven-3.6.0}}
> {{SET PATH=%M2_HOME%\bin;%PATH%}}
> {{cd ..}}
> {{cd *+c+*:\Temp\RelativelyInsane}}
> {{call mvn clean}}
> {{call mvn -vesion}}
> {{pause}}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
