As mentioned in http://issues.apache.org/bugzilla/show_bug.cgi?
id=37965, I've modified the 1.3 SyslogAppender to be API compatible
with 1.2. I've preserved the implementation changes in the 1.3
branch, but I suspect that the previous 1.3 branch code did not work
since its activateOptions method never called super.activateOptions()
which prevent any logging requests ever reaching it. If anyone has
an interest in the SyslogAppender and wants to evaluate the actual
usefulness of changes in the 1.3 branch, I would appreciate any
testing or comments that you have. I expect to move on to other
compatibility issues and would love somebody saving me having to come
back and see if it actually puts anything in the syslog.
I've updated the compatibility report at http://people.apache.org/
~carnold/compatibility.html.
I've also identified that running CLIRR with the current BCEL HEAD
(instead of the BCEL 5.1 bundled into CLIRR) eliminates the
NullPointerException's that I had previously encountered. To build
the compatibility report, use clirr-0.6.zip and build the BCEL head
(uses Maven 1.0) or steal one from Gump (http://vmgump.apache.org/
gump/public-jars/jakarta-bcel/jars/), copy build.properties.sample to
build.properties and modify appropriately.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
