logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Oliver Frietsch <da-mailing-lis...@friets.ch>
Subject Re: Up-to-date build instructions for Apache chainsaw?
Date Sun, 29 Jun 2008 11:55:17 GMT
Paul Smith schrieb:
>>
>> The junit error disappeared, yet two tests fail. Output attached in 
>> ZIP file...

In the extras package, TestLogMF fails. I attached the test result.

> Maven stores the detailed failures in a target subfolder.  In the 
> output, it mentions:
> 
> C:\Dokumente und Einstellungen\ThinkpadBenutzer\Eigene Dateien\Log4J 
> Workspace\log4j-chainsaw-maven\target\surefire-reports
> 
> containing the reports.
> 
> Could you please look for the failing test class file report in this 
> directory:
> 
> Running org.apache.log4j.chainsaw.prefs.MRUFileListTest
> Tests run: 2, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 0.08 sec 
> <<< FAILURE!
> Running org.apache.log4j.chainsaw.receivers.ReceiversHelperTest
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.01 sec 
> <<< FAILURE!
> Running org.apache.log4j.chainsaw.LogPanelPreferenceModelTest
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.01 sec 
> <<< FAILURE!
> 
> (these ones)

Sure, attached. I got the impression that my log4j hasn't compiled 
perfectly, even though it seemed so.

> If you run with '-Dmaven.test.skip=true' it should not bother running 
> these tests.  Are you doing this?

Yes.

> mvn -Dmaven.test.skip=true package
> 
> For Chainsaw, and then you should be able to launch Chainsaw from:
> 
> target/appassembler/bin/chainsaw (.bat if you're windows)

Exactly. That gave me this startup exception that I mentioned.

Oliver

Mime
View raw message