I should have noticed that it was during the :docs:javadoc task. subprojects/docs/docs.gradle is missing options.encoding = 'UTF-8'
Also interesting is that the javadoc options are extremely sparse compared to those specified in the grails/grails-core project gradle doc.gradle file (probably not a coincidence that there is a similarly named file with a similar build pattern) -Spencer --- On Tue, 8/30/11, Spencer Allain <[email protected]> wrote: From: Spencer Allain <[email protected]> Subject: Re: [gradle-dev] Re: Interesting character(s) in gradle source comment To: [email protected] Date: Tuesday, August 30, 2011, 10:23 AM I'll check on this later today when I'm home and see if I can figure out why it isn't applying UTF8 as the explicit encoding. -Spencer --- On Mon, 8/29/11, Peter Niederwieser <[email protected]> wrote: From: Peter Niederwieser <[email protected]> Subject: [gradle-dev] Re: Interesting character(s) in gradle source comment To: [email protected] Date: Monday, August 29, 2011, 11:38 PM Spencer Allain wrote: > > I got this when compiling the latest gradle source (pulled on Saturday) on > a local Windows 7 machine. I'm guessing whatever is happening is > defaulting to the character encoding of my console versus a specifically > assigned one. > Looks like a Java compiler warning to me. However I don't understand how this could happen given that we set the source encoding to UTF-8 for all projects (I just checked again). -- Peter Niederwieser Principal Engineer, Gradleware http://gradleware.com Creator, Spock Framework http://spockframework.org Twitter: @pniederw -- View this message in context: http://gradle.1045684.n5.nabble.com/Interesting-character-s-in-gradle-source-comment-tp4741837p4748725.html Sent from the gradle-dev mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
