You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Dennis Lundberg (JIRA)" <ji...@codehaus.org> on 2007/01/07 15:02:21 UTC
[jira] Closed: (SUREFIRE-56) Test is broken and marked as Fail but
works with plain execution with JUnit
[ http://jira.codehaus.org/browse/SUREFIRE-56?page=all ]
Dennis Lundberg closed SUREFIRE-56.
-----------------------------------
Resolution: Won't Fix
> Test is broken and marked as Fail but works with plain execution with JUnit
> ---------------------------------------------------------------------------
>
> Key: SUREFIRE-56
> URL: http://jira.codehaus.org/browse/SUREFIRE-56
> Project: surefire
> Issue Type: Bug
> Components: JUnit 3.x support
> Environment: Linux Mandriva 2007
> Windows W2k server
> Maven 2.04
> Reporter: Siegfried Klar
>
> we are using Castro for XML configuration processing.
> We wrote some Unit tests for the generation and the use of configuration to read in the app.
> If we execute this tests within the maven test cyle it breaks after
> (AppConfigs)Unmarshaller.unmarshal(AppConfigs.class, reader)
> And marks the test as failed. But if we run the test on commandline, without surefire ist works fine.
> Maybe we have a similar behaviour, if we run our MockEJB tests. These are also broken with Maven and Surefire.
> Any suggestions.
> Thanks in advance
> Siegfried Klar
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira