[logback-user] Building logback when tests fail

ceki ceki at qos.ch
Tue Oct 25 13:59:23 CEST 2011

Hi Thorbjørn,

Are you building from git master or from a released version? More inline.

On 25/10/2011 1:45 PM, Thorbjørn Ravn Andersen wrote:
> Hi.
> I am trying to set up Logback for development in order to write a
> JDK14Appender (based on the bridge) and my cloned source fails in
> testing with “[ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.6:test (default-test)
> on project logback-classic: There are test failures.” so I cannot run
> the "mvn package" command listed on the documentation page.

Can you provide more information on the test failures?

> Running “mvn -Dmaven.test.skip=true package” gives me “[ERROR] Failed to
> execute goal on project logback-classic: Could not resolve dependencies
> for project ch.qos.logback:logback-classic:jar:0.9.30-SNAPSHOT: Could
> not find artifact ch.qos.logback:logback-core:jar:tests:0.9.30-SNAPSHOT

Logback classic test requires logback-core-test.jar.

> I'd like to get this up and running in Eclipse but it is not quite easy
> even with both egit and Eclipse Maven plugins.

Logback now relies on both Groovy (GafferConfigurator) and Scala (for
tests) in addition to Java. IntelliJ IDEA deals with this particular
language configuration very nicely. I've heard that running
Groovy+Scala projects may be difficult to set up with Eclipse. I'd be
quite interested in your feedback in this regard.

> What would you suggest me to do to get up and running?

The current situation where Java+Groovy+Scala projects cannot be run
in Eclipse is rather problematic. It needs to be addressed asap.

More information about the Logback-user mailing list