Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.3
-
Fix Version/s: 2.4
-
Component/s: None
-
Labels:None
-
Complexity:Intermediate
-
Number of attachments :
Description
dependencies in a forked surefire instance should be avoided since any tests that use the same dependencies will be incompatible.
In this case, plexus-archiver, plexus-utils and plexus-container were introduced, causing any tests relying on newer versions of either to fail
Issue Links
| This issue is duplicated by: | ||||
| SUREFIRE-374 | incompatible class change error in surefire since the upgrade to the plexus archiver |
|
|
|
| This issue relates to: | ||||
| SUREFIRE-347 | regression: plexus is not properly isolated |
|
|
|
Jason suggested that we might use the maven-shade-plugin to shade our plexus dependencies (repackaging them in different package names and updating dependencies); it's a good idea, but maven-shade-plugin fails to work properly on the plexus archiver (it doesn't translate interfaces correctly, apparently?).