On 29 January 2013 17:12, Marcin Erdmann <[email protected]> wrote:
> Hi, > > Is there a particular reason for removing http://issues.gradle.org/** > browse/GRADLE-1267 <http://issues.gradle.org/browse/GRADLE-1267> from > scope? The issue was created as the outcome of this mailing list thread: > http://gradle.1045684.n5.**nabble.com/How-do-I-configure-** > a-file-encoding-for-the-**CopyTask-with-the-filter-for-** > replacing-tokens-td3311705.**html<http://gradle.1045684.n5.nabble.com/How-do-I-configure-a-file-encoding-for-the-CopyTask-with-the-filter-for-replacing-tokens-td3311705.html>. > It was scheduled to be fixed before 1.0 for some time but now it's not > scheduled any more. > I'm pretty sure this was done as part of a general issue cleanup. Previously we had a lot of issues "scheduled for 1.0" that for various reasons did not make the cut. > > I'm asking cause there has been a discussion on a JUG mailing list from my > hometown in Poland about Gradle and one of the participants has started to > migrate one of his Ant builds to Gradle. His views on Gradle are very > positive but he pinpointed the above mentioned issue as the biggest pain > for him ATM. Would you guys mind if picked it up in the near future? It > looks like making the encoding configurable for those tasks shouldn't be > all that hard. > Sure thing: a pull request would be most appreciated. Perhaps start with a proposal for how the DSL might look and any underlying changes required and circulate to this list. We can then iterate over that until we have a solid proposal, which can then be written up into a design doc, if deemed necessary. Adam might have some ideas on the best way to proceed, but if you want to kick off the design discussion that would be great. -- Darrell (Daz) DeBoer Principal Engineer, Gradleware http://www.gradleware.com
