You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "Julien HENRY (JIRA)" <ji...@codehaus.org> on 2009/07/16 10:24:22 UTC
[jira] Commented: (MRM-949) changing the consumers requires a
restart
[ http://jira.codehaus.org/browse/MRM-949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=183775#action_183775 ]
Julien HENRY commented on MRM-949:
----------------------------------
I can confirm this issue is still valid for Archiva 1.2.1.
I had to restart for repository-purge consumer activation being taken into account.
> changing the consumers requires a restart
> -----------------------------------------
>
> Key: MRM-949
> URL: http://jira.codehaus.org/browse/MRM-949
> Project: Archiva
> Issue Type: Improvement
> Components: web application
> Affects Versions: 1.1.2
> Reporter: Brett Porter
> Fix For: 1.x
>
>
> 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 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