[
http://jira.codehaus.org/browse/MRM-747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=194504#action_194504
]
Marc Lustig commented on MRM-747:
---------------------------------
hi Deng,
my idea was that xml-metadata etc. might be necessary to change even without
updating the actual artifact.
But this was just a suspicion.
You are certainly more familiar with Archiva's workflow - so please go ahead
and change it as you think its appropriate.
The first if-statement can also be changed I guess from
// check if artifact is a jar and verify if target repo is enabled for releases
// we suppose that release-artifacts can deployed only to repos enabled for
releases
if (resourcePath.endsWith("jar") &&
managedRepository.getRepository().isReleases())
{
to
// we suppose that release-artifacts can deployed only to repos enabled for
releases
if (managedRepository.getRepository().isReleases()) {
> 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
