On 02/09/2013 10:39, Francesco Chicchiriccò wrote:
Hi all,
at Syncope we are currently migrating from Logback to Log4j 2.0, as
per SYNCOPE-405 [1].
Our codebase is almost completely based on SLF4J API, so we are
evaluating the SLF4J bridge [2] (e.g. log4j-slf4j-impl): this works
almost fine, except for some classes (like as [3]) where we need to
programmatically set some logger levels.
I was able to do this with lo4j only by including log4j-core;
unfortunately it seems that including both log4j-slf4j-impl and
log4j-core generates some kind of block.
Am I doing something wrong?
We are using the last stable release (2.0-beta8).
In order to ease hunting, I have forked the Apache Syncope repository
and created a LOG4J2 branch on my own fork [4] that is using both
log4j-slf4j-impl and log4j-core: to reproduce, just clone, switch to the
LOG4J2 branch and:
$ mvn -PskipTests
$ cd core
$ mvn clean test
At this point the first unit test
(org.apache.syncope.core.connid.PasswordGeneratorTest) will hang.
Regards.
[1] https://issues.apache.org/jira/browse/SYNCOPE-405
[2] http://logging.apache.org/log4j/2.x/log4j-slf4j-impl/index.html
[3]
https://svn.apache.org/repos/asf/syncope/trunk/core/src/main/java/org/apache/syncope/core/init/LoggerLoader.java
[4] https://github.com/ilgrosso/syncope/tree/LOG4J2
--
Francesco Chicchiriccò
ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
http://people.apache.org/~ilgrosso/
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-user-h...@logging.apache.org
