commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brett Porter <>
Subject Re: [lang] doesn't build on Java 5
Date Sun, 19 Feb 2006 17:45:51 GMT
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

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
> 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:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message