Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Received-SPF: neutral (asf.osuosl.org: local policy)
Message-ID: <43F8AECF.1020804@apache.org>
Date: Mon, 20 Feb 2006 04:45:51 +1100
From: Brett Porter <brett@apache.org>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: Jakarta Commons Developers List <commons-dev@jakarta.apache.org>
Subject: Re: [lang] doesn't build on Java 5
References: <871wxzy9as.fsf@www.samaflost.de>
In-Reply-To: <871wxzy9as.fsf@www.samaflost.de>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

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