[jira] Closed: (MRM-860) maven metadata partly updated

["Brett Porter (JIRA)" <ji...@codehaus.org>]

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

Brett Porter closed MRM-860.
----------------------------

         Assignee: Brett Porter
       Resolution: Cannot Reproduce
    Fix Version/s:     (was: 1.2-M2)

there is not enough info to reproduce the issue - if it still occurs with 1.2, please reopen with what the metadata files look like and how the artifacts are deployed

> maven metadata partly updated
> -----------------------------
>
>                 Key: MRM-860
>                 URL: http://jira.codehaus.org/browse/MRM-860
>             Project: Archiva
>          Issue Type: Bug
>          Components: repository scanning
>    Affects Versions: 1.0.2
>         Environment: Linux server
>            Reporter: Anders Dvinge
>            Assignee: Brett Porter
>
> When i deploy a release or snapshot, to archiva, the metadata gets corrupted.
> The scenario is:
> I have a maven project with lets say 2 nested module
> 1. root project
>     1.1 nested 1
>     1.2 nested 2
> 1. When uploading the project
>     1.1 the metadata gets 'reset' by maven (with no release, latest etc.)
> 2. the scaning process is set to every 1 minute
>     2.2 the scanner corrects/updates the maven metadata
>           2.2.1 the 'root project' is correct
>           2.2.2 the 'nested 1' is INCORRECT (with no release, latest etc.) the scanner has't touched it
>           2.2.3 the 'nested 2' is correct
> I don't know if it is a coincidens that it is the first nested module hows metadata don't get updated. but that is what i have noticed in several projects.

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