[ http://issues.apache.org/jira/browse/PLUTO-236?page=all ]
David DeWolf resolved PLUTO-236.
--------------------------------
Fix Version/s: 1.1.0
Resolution: Fixed
I chose to leave out all logging from packaging and have removed all logging
configuration files from source. it should be up to the deployer to decide
what to use. Users can override the commons-logging default by adding these
files to shared/classes classpath instead of the WEB-INF/classes.
> Removal of log4j + logging configuration from web apps
> ------------------------------------------------------
>
> Key: PLUTO-236
> URL: http://issues.apache.org/jira/browse/PLUTO-236
> Project: Pluto
> Issue Type: Wish
> Components: portal driver, portlets-testsuite
> Affects Versions: 1.1.0-beta1
> Reporter: Tuomas Kiviaho
> Assigned To: David DeWolf
> Priority: Trivial
> Fix For: 1.1.0
>
> Attachments: logging.properties
>
>
> Is is possible to get rid of log4j. Commons logging should alone be enough.
> Also it would be nice if web app level ACL configurations would be removed so
> that container level would be preferred.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
