[
http://jira.codehaus.org/browse/MCOBERTURA-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=151625#action_151625
]
Justin Edelson commented on MCOBERTURA-88:
------------------------------------------
Is there a reason this patch hasn't been applied yet? There's no reason I can
see that Cobertura should run with a different classpath order than a normal
surefire run. If there's some ideological reason for keeping the pre-MNG-1412
behavior around, maybe that should be an option:
mvn -DrandomizeClasspath=true cobertura:cobertura
> Cobertura runs mess up project classpath
> ----------------------------------------
>
> Key: MCOBERTURA-88
> URL: http://jira.codehaus.org/browse/MCOBERTURA-88
> Project: Maven 2.x Cobertura Plugin
> Issue Type: Bug
> Affects Versions: 2.2
> Reporter: Michael Johns
> Attachments: MCOBERTURA-88.patch
>
>
> The fix for MNG-1412 took care of the random classpath ordering with
> projects, but a run of Cobertura reorders the classpath. Our unit tests run
> clean, but when we instrument our code first and then run the unit tests,
> they fail due to the plugin changing the classpath ordering.
> The fix for this is the same as the fix for MNG-1412, using LinkedHashSet
> rather than HashSet.
--
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
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
