[GRADLE-829] Add a native2ascii task based on Copy Created: 19/Feb/10  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: 0.9
Fix Version/s: None

Type: New Feature
Reporter: Peter Ledbrook Assignee: Unassigned
Resolution: Won't Fix Votes: 5

Attachments: File Native2AsciiCopySpecVisitor.groovy    


Ant's native2ascii task is fairly common in the web application world, so it would be great to have a dedicated Gradle copy task that does the same thing. As a starting point, I have attached a CopySpecVisitor implementation that can be slotted straight into a FileCopyActionImpl.

It's only a starting point, but it demonstrates how simple it is to set up. I'm willing to make changes if someone just directs me on what to do.

Comment by Adam Murdoch [ 24/Mar/10 ]

I wonder if this would be better implemented as a filter, so that it can work with any CopySpec based task (such as the archive tasks, or a future ftp/scp/webdav task)?

Comment by Peter Ledbrook [ 25/Mar/10 ]

I'm completely open to that idea. Wouldn't a CopySpecVisitor apply to all types of copy task as well, though? Regardless, we should do it in whatever is the standard way for Gradle so users have a consistent API to work with. I'm much less fussed what that standard approach is

Comment by Sviatoslav Romanenko [ 02/Feb/12 ]

My solution

war.dependsOn 'native2ascii'

task native2ascii << {

    ant.delete() {
        fileset(dir: "${processResources.destinationDir}") {
            include(name: 'bundle*.properties')
    ant.native2ascii(src: 'src/main/resources/',
            dest: "${processResources.destinationDir}",
            includes: '**/bundle*.properties',
            encoding: 'UTF-8')
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:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

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.

Generated at Wed Jun 30 11:40:00 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.