The problem is that we have included a logback.xml in the maven plugin (root level : warn) so your logback.xml set to debug doesn’t change anything : at your level, there’s nothing more to log.
But you can override the logback.xml included :
1/ with java -Dlogback.configurationFile=/path/to/config.xml
2/ with a logback-test.xml or logback.groovy in your classpath (Logback searches for these before searching for logback.xml, so the one included in the plugin jar would simply be skipped)
It’s no longer possible to specify the gatling.conf location.
However, every gatling.conf property can be overriding from the command line. For example, you can set -Dgatling.simulation.outputDirectoryBaseName=foo
i’ve tried this morning with Gatling 1.3.5 to set a JvmArg -Dgatling.http.provider=Apache to switch from Netty to Apache but it seems that it is still being used Netty.