![]() |
![]() |
|
Welcome
Guest
| Register
| Login
|
| Index | Recent Threads | Unanswered Threads | Who's Online | User List | Help |
|
|
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 3 |
|
| Author |
|
|
Novice Germany Joined: Aug 20, 2005 Post Count: 26 Status: Offline |
The question is how to set up the logging configuration using JDK logger for Maven plugin's enhance goal (I'm using the M2 plugin, but I guess it applies to the Maven1 plugin as well). Rationale: the ASM enhancer is too verbose, IMHO, using INFO level instead of DEBUG e.g. (see: recent thread). While log4.configuration is 'configurable' via the DataNucleus Maven plugin, the same is not true for JDK logger, as far as I read the docs and doing some code review, right? Workaround: Set DataNucleus.Enhancer.level=WARNING1) Define the JDK logger configuration on CMD like: mvn -Djava.util.logging.config.file=src/main/config/logging.properties clean install2) set it in the default config file: JDK_HOME/jre/lib/logging.propertiesSo, did I miss something that'll do the trick or is this issue worth a feature request concerning logger configuration in the Maven plugins? ---------------------------------------- André Fügenschuh |
||
|
|
Advanced Member Germany Joined: Jun 18, 2004 Post Count: 405 Status: Offline |
Yes, the maven2 enhancer plugin specifically is to verbose currently. Please file an issue in JIRA. |
||
|
|
Novice Germany Joined: Aug 20, 2005 Post Count: 26 Status: Offline |
To be precise, these are two different issues. a) Missing ability to configure JDK logging in the Maven plugin(s)! b) org.datanucleus.enhancer.asm.JdoClassChecker too verbose by default? So, I filed two RFE's in JIRA a) Maven Plugin: missing JDK logging configuration b) ASM: enhancement process too verbose ---------------------------------------- André Fügenschuh |
||
|
|
|
|
|
Current timezone is GMT Dec 2, 2008 3:25:25 PM |