Martin Poeschl wrote:
thanx to Ceki and Nicola for their posts!I think that given the latest changes in Avalon and the use if Avalon by Turbine, we can reasonably come up with a solution.
after reading all the post to the logging question it's still not clear how we can solve the problem.
turbine is not only the turbine.jar .. we use velocity, commons-packages, ...
all this packages use different logging packages (log4j, commons-logging, ...)
so it will not be possible to have one single logging mechanism for all of them ...
i think this is a problem which should be discussed on the general list .. it would be nice to have one logging mechanism used by all apache java projects (it's not only jakarta)
on the other hand i'm sure this will end in an endless discussion without any solution :-((
i really like log4j, but i understand the need to be able to use the jdk1.4 stuff (i still don't understand why sun didn't add log4j to the jdk .. but that's another story)I'd say, let's work to find a real solution that will end this anachronistic divide that has no technical base.
so commons-logging seems to solve this problem ...
as Ceki ponted out there are other problems with commons-logging ..
so maybe we should simple vote for log4j or commons-logging or avalon logging ... or logging to System.out ;-)
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
