[
http://jira.codehaus.org/browse/MRM-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=189730#action_189730
]
Wendy Smoak edited comment on MRM-1245 at 9/3/09 1:12 PM:
----------------------------------------------------------
Are you saying you uploaded/deployed a pom with a <dependency> that does not
exist? Actually, you picked the 'remote proxy' component, so is this a 'bad'
pom that was proxied in from a remote repository?
As far as I know, Archiva does not require transitive dependency closure of the
artifacts it manages.
What behavior would you like to see?
was (Author: wsmoak):
Are you saying you uploaded/deployed a pom with a <dependency> that does
not exist? Actually, you picked the 'remote proxy' component, so is this a
'bad' pom that was proxied in from a remote repository?
As far as I know, Archiva does not require transitive closure of the artifacts
it manages.
What behavior would you like to see?
> 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
