[
http://jira.codehaus.org/browse/MRM-809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=144655#action_144655
]
Wendy Smoak commented on MRM-809:
---------------------------------
This might be related to the file dates.
As discussed in the Archiva 1.1.1 vote thread, if you remove all the metadata
files, and scan the repo, it won't generate the metadata files again. But if
you 'touch' all the files and re-scan the repository, then it will generate
them for you.
While only scanning new content is good for the default case, there should be a
way to force it to scan, regardless of the file dates.
> 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
> Fix For: 1.1.x
>
>
> 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
