[logback-user] Building logback when tests fail

[Thorbjørn Ravn Andersen]

Thanks for a prompt reply.

I am building directly from a clone of git master.  Is there a specific tag
I should use to choose a suitable commit?

Maven reports:


Tests in error:
 
autoConfigFromSystemProperties(ch.qos.logback.classic.util.ContextInitialize
rTest)
  autoStatusListener(ch.qos.logback.classic.util.ContextInitializerTest)
 
autoOnConsoleStatusListener(ch.qos.logback.classic.util.ContextInitializerTe
st)
 
testGetExistingContext(ch.qos.logback.classic.selector.ContextJNDISelectorTe
st)
  testCreateContext(ch.qos.logback.classic.selector.ContextJNDISelectorTest)
  defaultContext(ch.qos.logback.classic.selector.ContextJNDISelectorTest)
  testDetach(ch.qos.logback.classic.selector.ContextDetachingSCLTest)
 
testDetachWithMissingContext(ch.qos.logback.classic.selector.ContextDetachin
gSCLTest)
  scan1(ch.qos.logback.classic.turbo.ReconfigureOnChangeTest)
  randomTest(ch.qos.logback.classic.turbo.ReconfigureOnChangeTest)
 
scanWithFileInclusion(ch.qos.logback.classic.turbo.ReconfigureOnChangeTest)
 
scanWithResourceInclusion(ch.qos.logback.classic.turbo.ReconfigureOnChangeTe
st)
 
includeScanViaInputStreamSuppliedConfigFile(ch.qos.logback.classic.turbo.Rec
onfigureOnChangeTest)
  gscan1(ch.qos.logback.classic.turbo.ReconfigureOnChangeTest)
  scan_lbclassic154(ch.qos.logback.classic.turbo.ReconfigureOnChangeTest)
  directPerfTest(ch.qos.logback.classic.turbo.ReconfigureOnChangeTest)
  indirectPerfTest(ch.qos.logback.classic.turbo.ReconfigureOnChangeTest)

Tests run: 374, Failures: 0, Errors: 17, Skipped: 10

You may have forgotten to check in some files?  Have your CI-engine reported
anything?

If you use IDEA and it works well, I'll have a go tomorrow.  We happen to
have a license for IntelliJ IDEA 9.

/Thorbjørn


-----Original Message-----
From: logback-user-bounces at qos.ch [mailto:logback-user-bounces at qos.ch] On
Behalf Of ceki
Sent: 25. oktober 2011 13:59
To: logback users list
Subject: Re: [logback-user] Building logback when tests fail

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.
--
Ceki
http://twitter.com/#!/ceki
_______________________________________________
Logback-user mailing list
Logback-user at qos.ch
http://mailman.qos.ch/mailman/listinfo/logback-user