[GRADLE-1141] Filtering in a copyspec is broken when a bare backslash is present in the input file. Created: 03/Sep/10 Updated: 10/Feb/17 Resolved: 10/Feb/17
|Reporter:||Jeroen van Erp||Assignee:||Unassigned|
When you filter files during the copy, using the expand(kay: value) method, it crashes when a bare backslash '\' character is present in the file.
Caused by: groovy.lang.GroovyRuntimeException: Failed to parse template script (your template may contain an error or be trying to use expressions not currently supported): startup failed:
Attached you can find the project to reproduce this.
|Comment by Andrew Phillips [ 06/Sep/10 ]|
According the the AbstractCopyTask docs , the input file is passed to the SimpleTemplateEngine  for processing. Since the SimpleTemplateEngine format uses '\' for escaping , the observed behaviour is to be expected.
However, I don't think it is "natural" to expect that text files in which users want to replace simple placeholders are written in the SimpleTemplateEngine format. Whilst that's an option that one might want to add for more advanced usage, I certainly think there's a case for a "dumb" string search-and-replace on files.
A workaround could be to use the Ant tasks for this, but since we're talking about the native Gradle copy task here it would seem odd if this only supported an "advanced" use case.
|Comment by Benjamin Muschko [ 15/Nov/16 ]|
As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.
We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.
Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:
We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!
|Comment by Benjamin Muschko [ 10/Feb/17 ]|
Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.