maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brett Porter (JIRA)" <>
Subject [jira] Moved: (SUREFIRE-103) 2.3-SNAPSHOT fails to deserialize an object due to ClassNotFoundException (regression)
Date Sun, 21 Jan 2007 22:02:19 GMT


Brett Porter moved MSUREFIRE-150 to SUREFIRE-103:

    Affects Version/s:     (was: 2.3)
                       2.0 (2.2 plugin)
        Fix Version/s:     (was: 2.3)
                  Key: SUREFIRE-103  (was: MSUREFIRE-150)
              Project: Maven Surefire  (was: Maven 2.x Surefire Plugin)

> 2.3-SNAPSHOT fails to deserialize an object due to ClassNotFoundException (regression)
> --------------------------------------------------------------------------------------
>                 Key: SUREFIRE-103
>                 URL:
>             Project: Maven Surefire
>          Issue Type: Bug
>    Affects Versions: 2.0 (2.2 plugin)
>            Reporter: Andrew Perepelytsya
>             Fix For: 2.3
>         Attachments: FAILED_org.mule.test.transformers.SerializedUMOMessageTransformersTestCase.txt,
FAILED_TEST-org.mule.test.transformers.SerializedUMOMessageTransformersTestCase.xml, org.mule.test.transformers.SerializedUMOMessageTransformersTestCase.txt,
RELEASE-m2-run.txt, SNAPSHOT-m2-run.txt, TEST-org.mule.test.transformers.SerializedUMOMessageTransformersTestCase.xml
> Ok, I know how tricky it can be to explain such bug, but I'll try. We've switched to
using 2.3-SNAPSHOT version of the plugin to get the fix for this error when test reports failed
the build in case of test errors without generating any report. This part works fine now,
but it has introduced a regression. 
> I'm attaching the test failure reports(it always worked before). To reproduce the error
(tricky part) - I can only think of checking out Mule project SVN source as of r2315 from What you need is only a top-level dir and mule-core.
> {panel}
> mvn test -Dtest=SerializedUMOMessageTransformersTestCase
> {panel}
> r2315 has 2.3-SNAPSHOT plugin version declared in a top-level pom. Change it to RELEASE,
and the problem is again gone.
> I'm also attaching m2 debug output for SNAPSHOT and RELEASE runs, hope it helps.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message