Running plugin with "own" classloader for slf4j in maven 3.2

Until Maven 3.0.x it was possible to run plugins that use slf4j with a
configuration of slf4j chosen by the project files (e.g. slf4j log4j binding
or a simplelogging config in the project), since Maven wasn't using slf4j
itself. Now in 3.2, the slf4j classes are loaded by Maven and so use the
ones that are stored in the lib and config dirs of Maven.

It is possible to remove the slf4j related files from maven and use other
ones instead, but I would prefer it if I could select the binding inside the
project. I assume that this requires some kind of classpath change to force
the plugin to use a new instance of slf4j and use the files select in the
project, but I have no idea how to do that (or if it is possible at all).

(the plugin I am currently using is vertx-maven-plugin, which basically runs
the whole project inside Maven)