[
http://jira.codehaus.org/browse/MAVENUPLOAD-1651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_105258
]
Jose M Beas commented on MAVENUPLOAD-1651:
------------------------------------------
I'm sorry, but I'm not sure I've understood the last posts.
Mauro: What do you mean when you say "Once that is released we'll upload both
artifacts."? What do you expect to be released? Who should release that?
Carlos: The last junit-4.4-bundle.jar file that I attached to this issue
contains (among other files) two jars: one with the source code and the other
with the compiled classes using the procedure in
http://maven.apache.org/guides/mini/guide-central-repository-upload.html
I've noticed that the jar with the binaries contains something in org.hamcrest
and I guess that's the "non-original" artifacts that you refer to.
How can I prevent those .class to be included in the jar file? I'm using scope
"compile" for hamcrest-core 1.1. Should I use a different scope for this?
Thanks,
JMB
> 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
