You are viewing an old version of this page. View the current version.
Compare with Current ·
View Page History
For advanced users, some tweakable bits for those who like to flip switches.
Logging Configuration
GMaven uses SLF4j and uses the Gossip provider to allow for simple and flexible configuration of logging output.
By default Gossip will use a reasonable default configuration. But if you feel like Maven is not spitting out enough information, or want to target the information displayed.
Try creating a $HOME/.gossip/config.properties file something like this:
version=1.0 profiles=groovy-debug profile.groovy-debug.triggers=debug profile.groovy-debug.trigger.debug=org.codehaus.groovy.maven.gossip.model.trigger.SystemPropertyTrigger profile.groovy-debug.trigger.debug.name=groovy-debug profile.groovy-debug.filters=console profile.groovy-debug.filter.console=org.codehaus.groovy.maven.gossip.model.filter.ConsoleWriter profile.groovy-debug.filter.console.renderer=org.codehaus.groovy.maven.gossip.model.render.SimpleRenderer profile.groovy-debug.filter.console.renderer.includeName=true profile.groovy-debug.filter.console.renderer.shortName=true profile.groovy-debug.filter.console.renderer.nameWidth=30 profile.groovy-debug.logger.org.codehaus.groovy.maven=DEBUG
And then flip it on by setting the groovy-debug property. Try it with the groovy:providers goal and see what it spits up.
mvn groovy:providers -Dgroovy-debug
Internal Logging Configuration
Sometimes you might need to see how the Gossip SLF4J provider is getting configured. To show Gossip's internal logging configure the org.codehaus.groovy.maven.gossip.InternalLogger system property, as in:
mvn groovy:providers -Dorg.codehaus.groovy.maven.gossip.InternalLogger.level=TRACE