[
http://jira.codehaus.org/browse/MRM-860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=165736#action_165736
]
James William Dumay commented on MRM-860:
-----------------------------------------
Anders, could you please try Archiva 1.2m1? I've redone the metadata merging in
this version which should solve weird issues like this one.
> 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
> Fix For: 1.2
>
>
> 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
