[
http://jira.codehaus.org/browse/MRM-809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter closed MRM-809.
----------------------------
Resolution: Won't Fix
Fix Version/s: (was: 1.4)
Assignee: Brett Porter
I agree with Wendy's assessment, and the forced scanning should take care of
this now. In the future, we should move these consumers to more general
'maintenance' tasks in which case they can run and confirm all the metadata
files are correct, independent of artifact scanning.
> metadata-updater does not add missing plugin versions to maven-metadata.xml
> file
> --------------------------------------------------------------------------------
>
> Key: MRM-809
> URL: http://jira.codehaus.org/browse/MRM-809
> Project: Archiva
> Issue Type: Bug
> Affects Versions: 1.0.2
> Reporter: Wendy Smoak
> Assignee: Brett Porter
>
> With the metadata-updater enabled, the maven-metadata.xml files are not
> updated to include plugin versions that are on the filesystem but not in the
> metadata file.
> We periodically copy one repo into another, which overwrites the metadata
> files. The source repository typically contains only one version of each
> plugin, whil we have multiple versions in the target repo. I expected
> Archiva to fix the metadata files in the target repo so that they list all of
> the versions again.
> (This probably applies to normal artifacts as well, but I've only been
> working with plugins.)
--
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
