[
http://jira.codehaus.org/browse/MRM-787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=133723#action_133723
]
Wendy Smoak commented on MRM-787:
---------------------------------
I think these could be flagged as problems on a report, but I'm not convinced
that Archiva should refuse to serve the pom when there is no jar.
There are some poms in central that have no associated jar, mainly the ones for
Sun jars that can't be redistributed.
http://repo1.maven.org/maven2/javax/ejb/ejb/2.0/
There is also the case of relocated artifacts, where there is only a pom
pointing to the new location, and no jar.
http://maven.apache.org/guides/mini/guide-relocation.html
> Don't allow partial artifacts to be accessed by maven.
> ------------------------------------------------------
>
> Key: MRM-787
> URL: http://jira.codehaus.org/browse/MRM-787
> Project: Archiva
> Issue Type: Bug
> Components: repository converter
> Reporter: Nick Pellow
>
> If an artifact's packaging is not pom, then the repository should not mark it
> the latest if only a pom is available.
> ie if an upload to the repository partly fails and for some reason the actual
> artifact is not available, do not let maven try to download that 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
