ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bickford, Mark" <Mark.Bickf...@wexinc.com>
Subject RE: Specify source file language in build.xml?
Date Wed, 18 Feb 2015 19:06:33 GMT
In my experience with Android, you can create an ant.properties which will be read at the start
of the build, and you should be able to set the java.encoding property there.

So far as the error itself goes, it came in with Java 7; I had source files with Microsoft
smart quotes in the comments that had to be repaired before they would compile.

-----Original Message-----
From: Peter West [mailto:lists@pbw.id.au] 
Sent: February 17, 2015 7:24 PM
To: Ant Users List; noloader@gmail.com
Subject: Re: Specify source file language in build.xml?

Are you able to modify the files?  iconv (on a unix-based system) will convert encodings.
Ideally, the files should be utf-8 encoded.  You can use iconv to try out suspected encodings
for the files, by converting from what you think may be the encoding to utf-8, and having
a look.  Once you've worked out the encoding, you can bulk convert the files, or just bulk
convert and copy to a working directory, and build from there.

I assume these files were created on a windows system?

Peter West
And they ate, and were satisfied...

> On 18 Feb 2015, at 7:35 am, Jeffrey Walton <noloader@gmail.com> wrote:
> 
> On Tue, Feb 17, 2015 at 4:26 PM, Earl Hood <earlhood@gmail.com> wrote:
>> On Tue, Feb 17, 2015 at 2:58 PM, Jeffrey Walton wrote:
>> 
>>>> Use the 'encoding' attribute to the <javac> task.
>> ...
>>>            <javac encoding="${java.encoding}"
>>>                    source="${java.source}" target="${java.target}"
>>>                    debug="true" extdirs="" includeantruntime="false"
>>>                    destdir="${out.classes.absolute.dir}"
>>>                    bootclasspathref="project.target.class.path"
>>>                    verbose="${verbose}"
>>>                    classpathref="project.javac.classpath"
>>>                    fork="${need.javac.fork}">
>>>                <src path="${source.absolute.dir}" />
>>>                <src path="${gen.absolute.dir}" />
>>>                <compilerarg line="${java.compilerargs}" />
>>>            </javac>
>> 
>> I do not know the specifics of how your build files are organized and if
>> you are using <ant> tasks to call other build files or you are including
>> all the build files so that targets are available directly.
>> 
>> With the fragment above, you need to set the java.encoding property.
>> You can do this from the command-line:
>> 
>>  ant -Djava.encoding=UTF-8 ...
> 
> That's what I was looking for! My dumb ass tried the following:
> 
>    $ /usr/local/bin/ant "java.encoding=ascii" release
>    Buildfile: /Users/android-permission-explorer/build.xml
> 
>    BUILD FAILED
>    Target "encoding=ascii" does not exist in the project "Permission Explorer".
> 
>> Command-line property settings have the highest precedence and will
>> override any setting in the build files.
>> ...
>> 
>> Note, java.encoding is not a default java system property, so something
>> is setting the property before the <javac> task is invoked.
> 
> Yeah, I'm beginning to think this is an Android problem.
> 
> Thanks for the help. Now that I have an idea of what I should do, I
> think I should pursue it on an Android list.
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
> For additional commands, e-mail: user-help@ant.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org


Mime
View raw message