You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Kristian Rosenvold (JIRA)" <ji...@codehaus.org> on 2011/04/11 15:07:22 UTC
[jira] Closed: (SUREFIRE-716) Don't skip deployment of
"common-junit3" and "common-junit4" artifacts
[ http://jira.codehaus.org/browse/SUREFIRE-716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Rosenvold closed SUREFIRE-716.
---------------------------------------
Resolution: Fixed
Fix Version/s: 2.8.1
Assignee: Kristian Rosenvold
Fixed in r1091057
> Don't skip deployment of "common-junit3" and "common-junit4" artifacts
> ----------------------------------------------------------------------
>
> Key: SUREFIRE-716
> URL: http://jira.codehaus.org/browse/SUREFIRE-716
> Project: Maven Surefire
> Issue Type: New Feature
> Reporter: Grzegorz Slowikowski
> Assignee: Kristian Rosenvold
> Priority: Minor
> Fix For: 2.8.1
>
>
> "common-junit3" and "common-junit4" artifacts are used by Surefire built-in jUnit providers. "common-junit*" artifacts code is shaded into these providers, and artifacts are not deployed (deployment is skipped).
> If someone wants to write custom jUnit provider, he cannot use "common-junit*" artifacts, because they are not present in Maven global repository (the workaround is to check out Surefire sources and install "commom-junit*" artifacts lokally).
> BTW, I don't thik shading "common-junit*" artifacts code into jUnit providers makes much sense. The code is shaded as is (no package name change or any other change).
--
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