You are viewing a plain text version of this content. The canonical link for it is here.
Posted to pluto-dev@portals.apache.org by "Tuomas Kiviaho (JIRA)" <ji...@apache.org> on 2006/04/28 12:15:38 UTC
[jira] Created: (PLUTO-236) Removal of log4j + logging
configuration from web apps
Removal of log4j + logging configuration from web apps
------------------------------------------------------
Key: PLUTO-236
URL: http://issues.apache.org/jira/browse/PLUTO-236
Project: Pluto
Type: Wish
Components: portal driver, portlets-testsuite
Versions: 1.1.0-beta1
Reporter: Tuomas Kiviaho
Priority: Trivial
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
[jira] Updated: (PLUTO-236) Removal of log4j + logging
configuration from web apps
Posted by "Craig Doremus (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/PLUTO-236?page=all ]
Craig Doremus updated PLUTO-236:
--------------------------------
Attachment: logging.properties
I got the logging to use the build-in Tomcat implementation of JDK 1.4+ (JUL) logging, which is what we use in Pluto 1.0.1. This also allows the removal of the commons-logging.properties, simplelog.properties and the commons-logging and log4j jars. A similar properties file could be adapted for the testsuite.
> 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
> 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
[jira] Assigned: (PLUTO-236) Removal of log4j + logging
configuration from web apps
Posted by "David DeWolf (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/PLUTO-236?page=all ]
David DeWolf reassigned PLUTO-236:
----------------------------------
Assignee: David DeWolf
> 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
>
> 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
[jira] Resolved: (PLUTO-236) Removal of log4j + logging
configuration from web apps
Posted by "David DeWolf (JIRA)" <ji...@apache.org>.
[ 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