On Apr 24, 2007, at 1:50 AM, Paul Smith wrote:
Sorry about the line-endings, hopefully I did better this time. I
was able to simplify the dependencies so that only one file
(jmxtools) needs to be manually downloaded and installed to build
log4j 1.2 on Java SE 5. I added explicit specifications to target
Java 1.3 or later and only accept Java 1.3 language features. I
specified the working directory for the unit tests which allowed
things to get started, but there are a decent number of failures.
Some are due to the tests not stripping out Maven's entries in the
stack traces. I cut and pasted some of the site reporting code
from one of the plugins. I thought, but refrained, from copying
over src/site and src/changes from one of the other projects, but
I am pretty tempted to make a shot at moving to a Maven generated
site and documentation.
I can't remember what exactly used to be the case, but was the
log4j 1.2 tree supposed to work on JDK 1.1+ I noticed just as you
posted that the new constructor in LoggingEvent takes a
java.util.Map, which was introduced in JDK 1.2. I just wouldn't
want us to completely break down compatibility. But perhaps that
already happened before? I dunno. I can't see too many people
being effected by this, but it's something to keep in mind.
Thanks. Will fix. Remind me to do an old JVM survey before release.
As per the site management, whatever makes our life easier, I can
start to see the benefit in putting a little Maven-effort into
things, over the long haul I think it does pay off. There was
nothing really wrong with the old way; slightly more manual, but
given Maven is starting to get more and more traction across Apache
projects I can't see why not.
Paul
I'll slide the src/changes and src/site stuff over from one of the
sandbox projects.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
