search

ColdMillenium / jwpl

Automatically exported from code.google.com/p/jwpl
0 stars 0 forks source link

[DataMachine, TimeMachine, RevisionMachine?] Correctly initialize log4j #49

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Log4j is not correctly initialized when the executable jars are run.

Original issue reported on code.google.com by oliver.ferschke on 17 Aug 2011 at 6:43

GoogleCodeExporter commented 9 years ago 
Also see Issue 62

Original comment by oliver.ferschke on 30 Nov 2011 at 2:37

GoogleCodeExporter commented 9 years ago 
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.

Original comment by richard.eckart on 30 Nov 2011 at 3:50

GoogleCodeExporter commented 9 years ago 
Issue 62 has been merged into this issue.

Original comment by oliver.ferschke on 5 Aug 2014 at 2:54

GoogleCodeExporter commented 9 years ago 
Added a standard log4j.properties properties file to src/main/resources

Original comment by oliver.ferschke on 5 Aug 2014 at 2:55

GoogleCodeExporter commented 9 years ago

Original comment by oliver.ferschke on 11 Sep 2014 at 1:36