Details
-
Type:
Bug
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 1.5.2
-
Fix Version/s: None
-
Component/s: Container
-
Labels:None
-
Environment:dev
-
Number of attachments :
Description
When doing plexus and mojo testing, its convienient to use PlexusTestCase.
The down side is PlexusTestCase extends TestCase
<code>
public abstract class PlexusTestCase
extends TestCase
</code>
From what I can tell, any test implementing PlexusTestCase will be considered by Junit 4.x to be legacy and not process the annotations in the test effectively putting the test into Junit 3.x syntax.
Since there are mountains of code using PlexusTestCase, probably the easiest way to deal with this is to create a "PlexusTester" abstract class and support Junit 3 and 4 for some time to come.