[
http://jira.codehaus.org/browse/MSHARED-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=194941#action_194941
]
Kathy Hale commented on MSHARED-121:
------------------------------------
It's funny you say that because I have the opposite problem. I'm using this bug
to disable the auto trigger because I couldn't find any way to disable it. So
if I need a path to remain unescaped (single backslashes, not doubled), I've
been breaking up the filter param like "${drive}${path}", such that ${drive} is
"{{C:}}" and {{${path}}} is "{{\path\}}."
> FilteringUtils.escapeWindowsPath doesn't handle paths that leave out the
> drive letter.
> --------------------------------------------------------------------------------------
>
> Key: MSHARED-121
> URL: http://jira.codehaus.org/browse/MSHARED-121
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-filtering
> Affects Versions: maven-filtering-1.0-beta-3
> Reporter: John Casey
> Fix For: maven-filtering-1.0-beta-4
>
> Attachments:
> 0001-MSHARED-121-Don-t-require-a-drive-letter-to-escape-a.patch,
> FilteringUtilsTest.java
>
>
> FilteringUtils.escapeWindowsPath requires a drive letter to be present in the
> path, or at least the string {noformat}":\\"{noformat} to be present in order
> to trigger escaping the value as a windows path.
> In cases where the path is an absolute reference to a file on the current
> drive (no drive letter is included), or when the path starts with an
> unresolved expression (in cases where n+1 level interpolation will eventually
> resolve the expression), escaping doesn't happen at all.
--
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