commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Barker" <wbar...@wilshire.com>
Subject Re: [lang] doesn't build on Java 5
Date Sun, 19 Feb 2006 18:03:14 GMT
Actually, the enum and Entities are just warnings.  The only actual error is 
in StrBuilder.StrBuilderWriter, and is caused by the fact that Writer 
aquired it's own append method in Java 5, so the one in StrBuilder is no 
longer visible.

"Brett Porter" <brett@apache.org> wrote in message 
news:43F8AECF.1020804@apache.org...
> That's just the first error. After that, there are a number of enum
> named variables (easy to fix), but also the "enum" package seems to be a
> problem.
>
> It could be changed to .enums, but that's not backwards compatible. IS
> that a reasonable change to make on trunk for c-l 3.0?
>
> - Brett
>
> Stefan Bodewig wrote:
>> Hi all,
>>
>> vmgump has switched to Java 5 (some will say finally) and commons-lang
>> fails there.  The reason are accented characters in Entities.java.
>>
>> Starting with Java 5 you have to specify the source file encoding to
>> javac explicitly if you want to reach beyond ASCII (I'm not sure
>> whether this is a bug or an intentional feature).
>>
>> I see two options, either user \uABCD escapes or specify
>> encoding="ISO-8859-1" (or whatever) to your Ant javac task (not sure
>> how to do that for Maven).
>>
>> Stefan
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>> 




---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message