Howard Lewis Ship gmail.com> writes:
>
> I looked at SLF4J earlier; at the time it wasn't thread safe.
> Switching over to it is still a possibility.
Hi Howard,
Good memory. I beleive that the thread safety issues were fixed about 10 months
ago. See also [1].
Please let me know if you need
I looked at SLF4J earlier; at the time it wasn't thread safe.
Switching over to it is still a possibility.
On 6/27/07, Renat Zubairov <[EMAIL PROTECTED]> wrote:
Hello,
We also had the same problem but apparently they can be solved without
changes from the Tapestry side.
You can modify your dep
Hello,
We also had the same problem but apparently they can be solved without
changes from the Tapestry side.
You can modify your dependencies in your pom.xml (I assuming you are
using maven) that tapestry and any tapestry dependency will not
include commons-logging jars in the WAR file, and inc
Is there a way to get commons-logging out of tapestry? I just fought with it
yet again the other day. Maybe a move to something like SLF4J? Commons
logging is really frustrating with it's classloader disaster always waiting
in the wings. The most comprehensive set of arguments against it are fou
