You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Stefan Bodewig <bo...@apache.org> on 2006/02/19 10:42:03 UTC
[lang] doesn't build on Java 5
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
Re: [lang] doesn't build on Java 5
Posted by Stefan Bodewig <bo...@apache.org>.
On Mon, 20 Feb 2006, Brett Porter <br...@apache.org> wrote:
> I don't know how I missed the "warning: " text on those :)
Hmm, so did I.
> I don't actually get the encoding warning on my machine.
I think vmgump's native encoding is UTF-8 while the source files are
ISO-8859-1.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [lang] doesn't build on Java 5
Posted by Brett Porter <br...@apache.org>.
I don't know how I missed the "warning: " text on those :) I don't
actually get the encoding warning on my machine.
I've fixed the inner class references.
- Brett
Bill Barker wrote:
> 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" <br...@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
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [lang] doesn't build on Java 5
Posted by Bill Barker <wb...@wilshire.com>.
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" <br...@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
Re: [lang] doesn't build on Java 5
Posted by Brett Porter <br...@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