[
http://jira.codehaus.org/browse/MRM-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=189767#action_189767
]
Wendy Smoak commented on MRM-1245:
----------------------------------
So you're saying that instead of sending 404 Not Found, Archiva is *inventing*
an invalid pom and jar?
Can you try it with the latest release (1.2.2) and see if it's still a problem?
> Archiva cache/create corrupt/invalid pom and jar in its internal directory
> --------------------------------------------------------------------------
>
> Key: MRM-1245
> URL: http://jira.codehaus.org/browse/MRM-1245
> Project: Archiva
> Issue Type: Bug
> Components: remote proxy
> Affects Versions: 1.1.4
> Environment: Linux
> Reporter: apache maillist
> Attachments: boguslog4j-1.0.0.jar, boguslog4j-1.0.0.pom
>
>
> Currently running 1.1.4, and when putting a dependency section that is not
> available internally or externally, Achriva creates/caches corrupt/invalid
> pom and jar in the internal directory
--
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
