Staging repo does not capture/reflect the config changes of the managed repo it
is attached to in MRM-980 branch
----------------------------------------------------------------------------------------------------------------
Key: MRM-1397
URL: http://jira.codehaus.org/browse/MRM-1397
Project: Archiva
Issue Type: Bug
Components: repository interface
Reporter: Maria Odea Ching
Steps to reproduce:
# Create a new managed repo named @test@ for releases and check Block
Re-deployment of Released Artifacts and Create stage repository.
# Upload a release-versioned artifact to the staging repository @test-stage@
through the web upload form
# Edit the configuration for repository @test@ and uncheck Block Re-deployment
of Released Artifacts, then Save the changes.
# Upload an artifact with the same artifact coordinates as the one uploaded in
step 2 to the staging repository @test-st...@. You'll get an error saying the
artifact is already in the repository even though you disabled blocking of
re-deployment of released artifacts.
--
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
