[
http://jira.codehaus.org/browse/MAVENUPLOAD-1651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_105284
]
Mauro Talevi commented on MAVENUPLOAD-1651:
-------------------------------------------
Artifacts will be released by the JUnit projects.
David has accepted the argument put forward in the thread
(http://thread.gmane.org/gmane.comp.java.junit.devel/1137/focus=15173) and will
be releasing both bundled and unbundled junit artifacts. I'll ping him to see
where we stand.
The whole point of having and unbundled artifact (ie with hamcrest as a
transitive dependency) is to prevent the problem you outline. Until we have
that we can't do anything about the hamcrest classes in the junit jar.
> junit 4.4
> ---------
>
> Key: MAVENUPLOAD-1651
> URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1651
> Project: maven-upload-requests
> Issue Type: Bug
> Reporter: Tomislav Stojcevich
> Assignee: Mauro Talevi
> Attachments: junit-4.4-bundle.jar, junit-4.4-bundle.jar,
> junit-4.4-bundle.jar
>
>
> Upload new version.
--
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
