Trouble with chainsaw source code and build today

[Lance Birtcil <La...@cnet.com>]

Hi,

First, thanks for all of the great work with log4j and chainsaw.  I swear by both.

Today I followed the instructions found here: http://logging.apache.org/log4j/docs/chainsaw.html to install chainsaw.  I ran into a nasty little problem when trying to build with 'ant chainsaw':

error: compiler message file broken: key=compiler.err.sun.io.MalformedInputException arguments=null, null, null, null, null, null, null

Luckily (or not) I've run into this before.  It's caused by 'strange' characters in the source files, like ellipsis, accents, copyright symbols, etc.  I wrote a little perl script to find the characters that were causing my build to fail, corrected them, and was able to build.  Here's what I found.

Open these two files in vi (not vim) and you should be able to see what I'm talking about.  (The character numbers may be slightly off, but they're close enough...)

....There's a ^M here that you can't see right after ...."pattern";
ERROR: ./java/org/apache/log4j/joran/action/ActionConst.java    has a bad character at line number 18, character number 60.
Here's the bad line>  public static final String PATTERN_ATTRIBUTE = "pattern";
  public static final String ACTION_CLASS_ATTRIBUTE = "actionClass";

.....The umlauts in Ceki's name are the problem here...replaced mine with ü
ERROR: ./java/org/apache/log4j/selector/ContextJNDISelector.java    has a bad character at line number 75, character number 32.
Here's the bad line> * <p>based primarily on Ceki Gülcü's article <h3>Supporting the Log4j

Hope this helps,
--Lance

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