[
https://jira.codehaus.org/browse/MRM-1652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=305426#comment-305426
]
Brett Porter commented on MRM-1652:
-----------------------------------
Those labels aren't great. At the moment they really just mean "don't scan for
releases", but we've slowly been making them more enforceable.
You could probably look at the section that does the 409 conflict if a release
is redeployed, that has the right checks if an artifact is considered a release
or not.
> Archiva should throw 405 (Method not allowed) when "releases=false" in
> archiva.xml
> ----------------------------------------------------------------------------------
>
> Key: MRM-1652
> URL: https://jira.codehaus.org/browse/MRM-1652
> Project: Archiva
> Issue Type: Bug
> Affects Versions: 1.4-M1
> Environment: RHEL 6
> Reporter: charles kim
> Assignee: Olivier Lamy
> Fix For: 1.4-M3
>
> Attachments: ArchivaDavResourceFactory_patch.txt
>
>
> releases is configured to false which should tell archiva that uploading
> should be disabled for the repo. But the setting doesn't work as seen from
> the code. Please see the attached patch. Thanks.
> <managedRepository>
>
> <location>/home/y/var/yarchiva/data/repositories/public</location>
> <blockRedeployments>true</blockRedeployments>
> <daysOlder>30</daysOlder>
> <id>public</id>
> <name>Archiva Managed Public Repository</name>
> <releases>false</releases>
> </managedRepository>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
