[
http://jira.codehaus.org/browse/MSHARED-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160884#action_160884
]
Casey Butterworth commented on MSHARED-78:
------------------------------------------
Unless there's a workaround that I'm not aware of, this defect is effectively
rendering the 2.3 resources plugin unusable for any projects that uses resource
filtering to directory locations (e.g. basedir) on windows, which I imagine is
a large number of projects. MRESOURCES-81 is a good description of the problem.
I've noticed that this is targeted at maven-filtering-1.0-beta-4, but i'm
wondering if it should not be in the next release instead, and also be
accompanied by a maven-release-plugin release?
> FilteringUtils escapeWindowsPath() doesn't work on Windows
> ----------------------------------------------------------
>
> Key: MSHARED-78
> URL: http://jira.codehaus.org/browse/MSHARED-78
> Project: Maven Shared Components
> Issue Type: Improvement
> Components: maven-filtering
> Affects Versions: maven-filtering-1.0-beta-2
> Reporter: Marvin Froeder
> Fix For: maven-filtering-1.0-beta-4
>
> Attachments: FilteringUtilsTest.java
>
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
