Closed aburmeis closed 10 years ago
We are experiencing this problem as well.
I won't get to it anytime soon. Would one of you guys be interested in a contributing a pull request for this?
Let me take a look.
Assign to me, I got this.
Great, thanks. Please also add at least one integration test.
Okay. I'm taking the encoding from the first available compiler (JavaCompile then GroovyCompile). I'll add an integration test to support this.
We should probably set it to UTF-8 by default.
tasks.withType(Compile) {
options.encoding = 'UTF-8'
}
I'm not familiar with the line above. Would this pass to the ant javac and groovyc tasks? If not, I have a pull request: https://github.com/bmuschko/gradle-clover-plugin/pull/45
Let me know what you'd prefer.
Ah, I forgot that we are calling Ant here. I think we can just set the encoding of the Ant task attribute encoding
to UTF-8
.
That would work too. Would you like a pull request for this as well? Is there any conceivable situation where a client would really want anything other than UTF-8? I can't think of one, but it's worth asking.
Let me know and I can do the busy work.
I am going to review the pull request soon and let you know. Probably won't happen today but this week. Thanks for your work.
Hey b, have you had a chance to check this one out? Cheers man.
Sorry, didn't find the time to do it yet.
Thanks for the followup. I'll post another request within the next two days.
Another go-round. Let me know what you think.
Re-re-Posted here https://github.com/bmuschko/gradle-clover-plugin/pull/47
Please investigate at your earliest convenience.
When using the clover plugin, some tests containing UTF-8 characters in assertions fail on some machines. I think the default encoding is used. An option to set the source encoding should be offered!