[
http://jira.codehaus.org/browse/MAVENUPLOAD-1651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103868
]
Mauro Talevi commented on MAVENUPLOAD-1651:
-------------------------------------------
I'm actually advocating the exact opposite: for me bundling dependency classes
in the junit jar is a very bad decision. IMO it motivated primarily by the
perceived "simplicity" of having a single jar rather than two or more. In
fact, it is a recipe for a classloader quagmire when hamcrest jars are also
present in the classpath.
I've argued this on the junit list and I've had no reply. So - respectful of
other projects decisions, even when not in agreement with them - I think the
least common denominator is to upload *both* a junit artifact - as released by
the project - and a junit-dep which has the hamcrest 1.1 dependency as a
transitive dependency. Then people will be free to choose what they want to
use.
> 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
>
>
> 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
