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 2015/02/11 11:55:18 UTC

[jira] (MRM-949) changing the consumers requires a restart

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

Olivier Lamy updated MRM-949:
-----------------------------

    Fix Version/s:     (was: 2.2.0)
                   2.3.0

> changing the consumers requires a restart
> -----------------------------------------
>
>                 Key: MRM-949
>                 URL: https://jira.codehaus.org/browse/MRM-949
>             Project: Archiva
>          Issue Type: Improvement
>          Components: Web Interface
>    Affects Versions: 1.1.2
>            Reporter: Brett Porter
>             Fix For: 2.3.0
>
>
> it seems that at present the configuration notification is not reaching the consumer delegation. The specific one I was enabling was the repository purge.
> This may be best targeted at 1.2 and a review of configuration and particularly change notification since there are a few gaps occurring. I believe rather than using a text string it would be better to simply inspect the relevant configuration on every change and let the configured object decide how to handle the event.
> It would be best aligned to the upcoming event architecture as well



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)