If you want to drive into this, you may want to review the LogMF and LogSF
companions and related discussion in the archives.
The cost of the array construction implicit in a vararg call and the cost of
boxing scalars can dwarf the cost of determining whether to log or not.
Unfortunately those
Apache log4j 2.0 has been a long simmering bunch of wish lists and a little
experimental code waiting for a sufficient community to assemble to start
fleshing things out. Not sure if we are there yet, but looks like there is
some signs of life and it would be good to have as many perspectives a
Thanks for this nice script !
Should I update the "candidate" folder with the generated jars an
call for a
vote ?
Nico.
The first version of the script was written to verify your process.
I've slightly modified the script to improve the generated jars. The
new script (http://people
I wrote an Ant script that attempts to mimic the platform specific
script used to prepare the current candidates. The script also can
compare the candidate against the locally prepared source jars to
determine any inconsistencies.
The script is available at http://people.apache.org/~carnol
On Feb 2, 2008, at 2:08 PM, nicolas de loof wrote:
on [EMAIL PROTECTED],
http://mail-archives.apache.org/mod_mbox/www-repository/200802.mbox/thread
LICENSE, NOTICE and other *.txt files (release note, readme ...) have
been added at jar root.
I can rebuild the jars with those files in META-IN
