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" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > 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: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
