[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
[jetty-users] Maven plugin ignores slf4j
|
Something seems to be broken with the Jetty Maven plugin. If I run Jetty
using exec:exec:
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>exec-maven-plugin</artifactId>
<version>1.2</version>
<executions>
<execution>
<goals>
<goal>exec</goal>
</goals>
</execution>
</executions>
<configuration>
<executable>java</executable>
<arguments>
<argument>-classpath</argument>
<classpath/>
<argument>-ea</argument>
<argument>com.foo.Main</argument>
</arguments>
</configuration>
</plugin>
Then slf4j logging works. If I use jetty:run instead:
<plugin>
<groupId>org.mortbay.jetty</groupId>
<artifactId>jetty-maven-plugin</artifactId>
<version>7.4.4.v20110707</version>
<configuration>
<scanIntervalSeconds>5</scanIntervalSeconds>
<connectors>
<connector
implementation="org.eclipse.jetty.server.nio.SelectChannelConnector">
<port>80</port>
</connector>
</connectors>
</configuration>
</plugin>
Then slf4j logging does not work. I want to emphasize the fact that the
pom.xml file is *identical*. The only thing I am changing is whether I'm
invoking exec:exec or jetty:run. Hence, this can't be a simple dependency
problem (my project depends on logback-classic).
My guess is that the Maven plugin is ignoring the project classpath.
Gili
--
View this message in context: http://jetty.1047016.n5.nabble.com/Maven-plugin-ignores-slf4j-tp4750433p4750433.html
Sent from the jetty-users mailing list archive at Nabble.com.