Details
-
Type:
Improvement
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: maven-filtering-1.0-beta-2
-
Fix Version/s: maven-filtering-1.0-beta-4
-
Component/s: maven-filtering
-
Labels:None
-
Testcase included:yes
-
Patch Submitted:Yes
-
Number of attachments :
Description
The method escapeWindowsPath() is replacing colon by backslash + colon.
I.e.
D:\temp
is escaped as
D\:
temp
But windows doesn't recognize that. If you try to open D\:
temp on explorer, will not work.
Even java.io.File is not able to handle that too. The attached test proves it.
I'm not sure why this backslash was add to colon, but commenting line 44 of org.apache.maven.shared.filtering.FilteringUtils make the test work.
Issue Links
- is depended upon by
-
MRESOURCES-81
2.3 escapes characters when filtering properties
-
- is related to
-
MRESOURCES-42
Filtering properties that contain ${basedir} for property files doesn't escape backslashes
-
-
MRESOURCES-81
2.3 escapes characters when filtering properties
-
- relates to
-
MRESOURCES-106
Plugin does not respect escapeWindowsPaths default-value
-
At
MRESOURCES-42was suggested to escape colon too.I have no idea why, but this doesn't work on windows.