Details
-
Type:
Improvement
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 1.1.2
-
Fix Version/s: 1.4
-
Component/s: Web Interface
-
Labels:None
-
Number of attachments :
Description
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
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.