ReplaceRegexp problem with newline as replace string

[dthomas]

The documentation of the ReflexiveTask contains the following example:

<reflexive>

<fileset ... />
<filterchain>

<replaceregexp>

<regexp pattern="\n\r" replace="\n"/>

</replaceregexp>

</filterchain>

</reflexive>

But the modified files contain the string "\n" instead of the expected newline.

PS: shouldn't the pattern be "\r\n" instead for windows?

[mrook]

Fixed in r346, thanks!

[michaelze]

I know this is a very old ticket, but in my opinion, this issue is not resolved.

I think the intention of the OP was not to hint the small mistake in the documentation but to point out that newlines in the replace attribute of the <regexp /> element do not appear as newlines in the replaced text but as the two characters "\" and "n".

Although this issue is over 3 years old, this still exists in v2.4.5.

[anonymous]

It can be worked around by using:

<regexp pattern="\r\n" replace="${line.separator}"/>

[anonymous]

${line.separator} returns the value of PHP_EOL which is \r\n on Windows. If you're processing files on Windows but do need \n (line feed) as line separator:

<php expression="chr(10)" returnProperty="LF"/>
...
<regexp pattern="\n\r" replace="${LF}"/>