[jira] Closed: (MRM-377) Previous repository configuration doesn't reflect in the Edit Repository page

["Maria Odea Ching (JIRA)" <ji...@codehaus.org>]

     [ http://jira.codehaus.org/browse/MRM-377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maria Odea Ching closed MRM-377.
--------------------------------

    Resolution: Fixed

Applied submitted patch -r542496. Thanks!

> Previous repository configuration doesn't reflect in the Edit Repository page
> -----------------------------------------------------------------------------
>
>                 Key: MRM-377
>                 URL: http://jira.codehaus.org/browse/MRM-377
>             Project: Archiva
>          Issue Type: Bug
>          Components: repository interface
>            Reporter: Dawn Angelito
>            Assignee: Maria Odea Ching
>         Attachments: MRM-377-archiva-webapp.patch
>
>
> Steps:
> 1) Log in as admin.
> 2) On the left menu, under Administration, click Repositories.
> Please take note of the default values for Archiva Managed Internal Repository:
>      Releases Included - true
>      Snapshots Included - false
>      Scanned - true
> 3) Edit this repository.
> Notice that in the Edit Repository page of Archiva Managed Internal Repository, Releases Included, Snapshots Included and Scanned were all unchecked. 
> Note: Same goes with Archiva Managed Snapshot Repository. The previous repository configuration doesn't reflect in the Edit Repository page.

-- 
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