I don't. I use the pluto:install and it installs the entire portal and
testsuite for me. I simply start up tomcat afterwards and it logs how I
have things configured in my commons-logging.properties file.
That said, I do have logkit, avalon, and log4j dependencies in
WEB-INF/lib. We could definately get rid of those if we want to -
especially the former two.
We could also depend upon commons-logging-api-1.1 instead of the core
and loose those dependencies. Why are you removing 1.1 in lieu of 1.0.4
anyways?
David
Elliot Metsger wrote:
I have a question about configuring logging for the pluto portal. Maybe
I'm missing something.
Everytime I deploy a fresh build of pluto to tomcat, I have to shuffle
jar files around to get output in <TOMCAT_HOME>/logs/pluto-YYYY-MM-DD.log:
rm webapps/pluto/WEB-INF/lib/commons-logging-1.1.jar
rm webapps/pluto/WEB-INF/lib/log4j-1.2.12.jar
cp webapps/testsuite/WEB-INF/lib/commons-logging-1.0.4.jar
webapps/pluto/WEB-INF/lib/commons-logging-1.0.4.jar
Does anyone else have this problem? If not forget it it must just be me.
Regardless, commons-logging-1.1 pulls in the following:
pluto-portal->pluto-portal-driver->spring-web->commons-logging-1.1
commons-logging-1.1-> log4j.1.2.12
commons-logging-1.1-> logkit-1.0.1
commons-logging-1.1-> avalon-framework-4.1.3
