[jbpm-issues] [JBoss JIRA] Updated: (JBPM-2021) remove logging.properties from the enteprise classpath
[
https://jira.jboss.org/jira/browse/JBPM-2021?page=com.atlassian.jira.plug...
]
Tom Baeyens updated JBPM-2021:
------------------------------
Summary: remove logging.properties from the enteprise classpath (was: JBPM logs
to stderr)
Fix Version/s: jBPM 4.0.0.Beta1
(was: jBPM 4.0.0.GA)
Heiko, in the container, the idea is that no logging.properties should be on the classpath
when running in jboss. Then jBPM will just use Log4J, since it is on the classpath in the
container.
remove logging.properties from the enteprise classpath
------------------------------------------------------
Key: JBPM-2021
URL: https://jira.jboss.org/jira/browse/JBPM-2021
Project: JBoss jBPM
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Core Engine
Reporter: Heiko Braun
Fix For: jBPM 4.0.0.Beta1
Taken from the enterprise tests (running inside AS)
2009-02-06 10:05:46,847 ERROR [STDERR] (http-127.0.0.1-8080-1) Feb 6, 2009 10:05:46 AM
org.jbpm.log.Jdk14Log debug
FINE: creating environment factory for jbpm.cfg.xml
Why a custom logging implementation anyway?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira