Issue 49 in jwpl: [DataMachine, TimeMachine, RevisionMachine?] Correctly initialize log4j

[jw...@googlecode.com]

Status: Accepted
Owner: oliver.ferschke
Labels: Type-Defect Priority-Low

New issue 49 by oliver.ferschke: [DataMachine, TimeMachine,
RevisionMachine?] Correctly initialize log4j
http://code.google.com/p/jwpl/issues/detail?id=49

Log4j is not correctly initialized when the executable jars are run.

[jw...@googlecode.com]

Comment #1 on issue 49 by oliver.ferschke: [DataMachine, TimeMachine,

RevisionMachine?] Correctly initialize log4j
http://code.google.com/p/jwpl/issues/detail?id=49

Also see Issue 62

[jw...@googlecode.com]

Comment #2 on issue 49 by richard....@gmail.com: [DataMachine, TimeMachine,

RevisionMachine?] Correctly initialize log4j
http://code.google.com/p/jwpl/issues/detail?id=49

How about manually setting up reasonable logging levels in the main()
methods? BasicConfigurator.configure() is probably not good because it sets
everything to debug. I think there is some property configurator where you
can explicitly say the name of the properties file. If you use a different
name than log4j.properties, and explicitly read from that, I suppose that
should be fine. Of course only when actual main() methods are used.

[jw...@googlecode.com]

Comment #3 on issue 49 by oliver.ferschke: [DataMachine, TimeMachine,

RevisionMachine?] Correctly initialize log4j
http://code.google.com/p/jwpl/issues/detail?id=49

Issue 62 has been merged into this issue.

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[jw...@googlecode.com]

Updates:
Status: Fixed
Labels: Milestone-Release-0.10.0

Comment #4 on issue 49 by oliver.ferschke: [DataMachine, TimeMachine,

RevisionMachine?] Correctly initialize log4j
http://code.google.com/p/jwpl/issues/detail?id=49

Added a standard log4j.properties properties file to src/main/resources