[
http://jira.codehaus.org/browse/MRM-747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=194528#action_194528
]
Maria Odea Ching commented on MRM-747:
--------------------------------------
Yeah, the metadata and support files (checksums, gpg signatures, etc.) should
be allowed to continue in the deployment. Maven would not continue deploying
them if the artifact deployment failed. I updated the patch and added a check
for this instead of specific to jar files. I also added tests for deploying
metadata and checksum files. I'll apply and commit the fix shortly. Thanks
again Marc!
> Archiva should prevent re-deployment of released or non-snapshot versioned
> artifacts
> ------------------------------------------------------------------------------------
>
> Key: MRM-747
> URL: http://jira.codehaus.org/browse/MRM-747
> Project: Archiva
> Issue Type: Bug
> Components: WebDAV interface
> Affects Versions: 1.0.1
> Reporter: Alexandre Navarro
> Assignee: Maria Odea Ching
> Fix For: 1.2.3
>
> Attachments: ArchivaDavResourceFactory.java, MRM-747.diff,
> MRM-747.svndiff, MRM-747_trunk.diff,
> ReleaseArtifactAlreadyExistsException.java
>
>
> It is possible de redeploy a versionned jar with webdav eventhough it must be
> impossible.
> It is possible de redeploy a versionned jar eventhough the file is readonly.
> It is very problematic.
--
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
