[jira] Updated: (MSUREFIRE-150) 2.3-SNAPSHOT fails to deserialize an object due to ClassNotFoundException (regression)

2006-07-31 Thread Brett Porter (JIRA)
 [ http://jira.codehaus.org/browse/MSUREFIRE-150?page=all ]

Brett Porter updated MSUREFIRE-150:
---

Fix Version/s: 2.3

> 2.3-SNAPSHOT fails to deserialize an object due to ClassNotFoundException 
> (regression)
> --
>
> Key: MSUREFIRE-150
> URL: http://jira.codehaus.org/browse/MSUREFIRE-150
> Project: Maven 2.x Surefire Plugin
>  Issue Type: Bug
>Affects Versions: 2.3
>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 http://svn.codehaus.org/mule/ 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: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] Updated: (MSUREFIRE-150) 2.3-SNAPSHOT fails to deserialize an object due to ClassNotFoundException (regression)

2006-07-24 Thread Andrew Perepelytsya (JIRA)
 [ http://jira.codehaus.org/browse/MSUREFIRE-150?page=all ]

Andrew Perepelytsya updated MSUREFIRE-150:
--

Attachment: 
FAILED_TEST-org.mule.test.transformers.SerializedUMOMessageTransformersTestCase.xml

FAILED_org.mule.test.transformers.SerializedUMOMessageTransformersTestCase.txt

> 2.3-SNAPSHOT fails to deserialize an object due to ClassNotFoundException 
> (regression)
> --
>
> Key: MSUREFIRE-150
> URL: http://jira.codehaus.org/browse/MSUREFIRE-150
> Project: Maven 2.x Surefire Plugin
>  Issue Type: Bug
>Affects Versions: 2.3
>Reporter: Andrew Perepelytsya
> 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 http://svn.codehaus.org/mule/ 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: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] Updated: (MSUREFIRE-150) 2.3-SNAPSHOT fails to deserialize an object due to ClassNotFoundException (regression)

2006-07-24 Thread Andrew Perepelytsya (JIRA)
 [ http://jira.codehaus.org/browse/MSUREFIRE-150?page=all ]

Andrew Perepelytsya updated MSUREFIRE-150:
--

Attachment: SNAPSHOT-m2-run.txt

> 2.3-SNAPSHOT fails to deserialize an object due to ClassNotFoundException 
> (regression)
> --
>
> Key: MSUREFIRE-150
> URL: http://jira.codehaus.org/browse/MSUREFIRE-150
> Project: Maven 2.x Surefire Plugin
>  Issue Type: Bug
>Affects Versions: 2.3
>Reporter: Andrew Perepelytsya
> Attachments: 
> 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 http://svn.codehaus.org/mule/ 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: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] Updated: (MSUREFIRE-150) 2.3-SNAPSHOT fails to deserialize an object due to ClassNotFoundException (regression)

2006-07-24 Thread Andrew Perepelytsya (JIRA)
 [ http://jira.codehaus.org/browse/MSUREFIRE-150?page=all ]

Andrew Perepelytsya updated MSUREFIRE-150:
--

Attachment: RELEASE-m2-run.txt

TEST-org.mule.test.transformers.SerializedUMOMessageTransformersTestCase.xml

org.mule.test.transformers.SerializedUMOMessageTransformersTestCase.txt

> 2.3-SNAPSHOT fails to deserialize an object due to ClassNotFoundException 
> (regression)
> --
>
> Key: MSUREFIRE-150
> URL: http://jira.codehaus.org/browse/MSUREFIRE-150
> Project: Maven 2.x Surefire Plugin
>  Issue Type: Bug
>Affects Versions: 2.3
>Reporter: Andrew Perepelytsya
> Attachments: 
> 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 http://svn.codehaus.org/mule/ 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: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira