You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@archiva.apache.org by "Olivier Lamy (JIRA)" <ji...@codehaus.org> on 2011/09/12 09:31:07 UTC

[jira] Commented: (MRM-1332) remove database scanning configuration and handle upgrade

    [ https://jira.codehaus.org/browse/MRM-1332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=278308#comment-278308 ] 

Olivier Lamy commented on MRM-1332:
-----------------------------------

IMHO could me marked as fixed ? @Brett ?

> remove database scanning configuration and handle upgrade
> ---------------------------------------------------------
>
>                 Key: MRM-1332
>                 URL: https://jira.codehaus.org/browse/MRM-1332
>             Project: Archiva
>          Issue Type: Task
>          Components: system
>    Affects Versions: 1.4
>            Reporter: Brett Porter
>             Fix For: 1.4-M1
>
>
> the configuration file still contains the database scanning information. This isn't harmful, but it can be removed. This will require a version bump and proper migration from a previous configuration version.
> We need to ensure that the metadata creation consumer is enabled by default, otherwise project models will not be correctly populated.
> We need to make sure that the duplicate artifact consumer (that checks if two checksums are identical) is migrated from the database scanning section to the known content scanning section.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira