Thanks, I will take a look how to implement that.
I've seen 3 people ask about this thus far but making this mechanism
configurable for servers that need to run inside Maven is not high on my
priority list.
Can you not just fork and then use the runtime as it would be launched in
production. Run
When I include logback in the project, it just keeps using the simple logger,
there is no message about multiple bindings.
You can swap slf4j-simple against Logback if you like. As far as I know,
plugins are isolated aren't they? Does SLF4J report duplicate bindings
if you try so?
--
View
I've seen 3 people ask about this thus far but making this mechanism
configurable for servers that need to run inside Maven is not high on my
priority list.
Can you not just fork and then use the runtime as it would be launched in
production. Running app servers inside Maven in general I don't
Am 2014-06-17 21:34, schrieb alexlehm:
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 classe
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
