On 24/11/2011 15:45, Thorsten Scherler wrote:
Hi all,
I noticed that if you do
mvn clean install jetty:run
on e.g. cocoon-sample
You will get target/rcl/webapp/WEB-INF/log4j.xml and an appContext that
points to log4j.
Where is this coming from? I would like to update that to only use
logback.xml as we do in
archetype-webapp/src/main/resources/archetype-resources/src/main/webapp/WEB-INF/applicationContext.xml
Any pointers?
Hi,
cocoon-sample depends on cocoon-rcl-webapp-wrapper [1], which in turns
depends on log4j.
However, if you do "mvn clean package jetty:run" on cocoon-sample-webapp
(instead of cocoon-sample), you won't find any trace of log4j any more.
Unfortunately, there are quite some dependencies that I guess were
initially thought for C2.2, then used for C3 and now getting old like as:
* cocoon-spring-configurator: think that I had to put replacement of
Log4JConfigurator, LogbackConfigurator, in cocoon-servlet [2]
* cocoon-rcl-webapp-wrapper
* cocoon-xml: think that I had to put ParamSAXBuffer extending
SAXBuffer in cocoon-sax [3]
I think we should decide how to cope with this.
Regards.
[1]
https://svn.apache.org/repos/asf/cocoon/tags/cocoon-2.2/cocoon-rcl-webapp-wrapper/cocoon-rcl-webapp-wrapper-1.0.0/pom.xml
[2]
http://old.nabble.com/Re%3A--C3--replacing-the-logging-framework-p32226435.html
[3] http://old.nabble.com/Re%3A--C3--i18n-support-p32242981.html
--
Francesco Chicchiriccò
Apache Cocoon Committer and PMC Member
http://people.apache.org/~ilgrosso/
