[ 
https://jira.codehaus.org/browse/MASSEMBLY-674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Lundberg updated MASSEMBLY-674:
--------------------------------------

    Description: 
Using <escapeString>\</escapeString>   does not correctly when dealing with 
case where previous text is also a \.
attached pom,test and assembly.xml show what happens. The follwoing scenario is 
currently fail:  (varible=Hello)
{code}
C:\path\\${variable}
{code}
converted to 
{code}
C:\path\\Hello
{code}
I would of expected:
{code}
C:\path\${variable}
{code}

The following does work but is not exactly as required as it means you get get 
two \'s
{code}
C:\path\\\${variable}
{code}
converted to
{code}
C:\path\\${variable}
{code}


  was:
Using <escapeString>\</escapeString>   does not correctly when dealing with 
case where previous text is also a \.
attached pom,test and assembly.xml show what happens. The follwoing scenario is 
currently fail:  (varible=Hello)

C:\path\\${variable}   converted to  C:\path\\Hello
I would of expected: C:\path\${variable}

The following does work but is not exactly as required as it means you get get 
two \'s
C:\path\\\${variable}  converted to  C:\path\\${variable}




I think we need to add another option for filtering, like this one:
http://maven.apache.org/plugins/maven-resources-plugin/resources-mojo.html#escapeWindowsPaths

> escapeString using \ does not work correctly
> --------------------------------------------
>
>                 Key: MASSEMBLY-674
>                 URL: https://jira.codehaus.org/browse/MASSEMBLY-674
>             Project: Maven Assembly Plugin
>          Issue Type: Improvement
>          Components: filtering
>    Affects Versions: 2.4
>            Reporter: Iain Coulter
>            Priority: Minor
>             Fix For: 2.5
>
>         Attachments: escapeStringBug.zip
>
>
> Using <escapeString>\</escapeString>   does not correctly when dealing with 
> case where previous text is also a \.
> attached pom,test and assembly.xml show what happens. The follwoing scenario 
> is currently fail:  (varible=Hello)
> {code}
> C:\path\\${variable}
> {code}
> converted to 
> {code}
> C:\path\\Hello
> {code}
> I would of expected:
> {code}
> C:\path\${variable}
> {code}
> The following does work but is not exactly as required as it means you get 
> get two \'s
> {code}
> C:\path\\\${variable}
> {code}
> converted to
> {code}
> C:\path\\${variable}
> {code}



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

Reply via email to