ahgittin opened a new pull request #277: URL: https://github.com/apache/brooklyn-ui/pull/277
(1) metadata service appeared to have an inconsistent naming strategy; when i updated the PID/name as done here it worked perfectly, matching the location metadata cfg files we install. (2) this also seems to for now get rid of these errors in the startup log ``` 2021-09-01T09:07:05,357 - ERROR 374 o.a.b.u.m.ExternalUiModule [FelixStartLevel] bundle org.apache.brooklyn.ui.modularity.brooklyn-ui-external-modules:1.1.0.SNAPSHOT (374)[org.apache.brooklyn.ui.modularity.ExternalUiModule] : Cannot register component 2021-09-01T09:07:05,372 - ERROR 375 o.a.b.u.m.m.r.i.UiMetadataConfigListener [FelixStartLevel] bundle org.apache.brooklyn.ui.modularity.brooklyn-ui-metadata-registry:1.1.0.SNAPSHOT (375)[org.apache.brooklyn.ui.modularity.metadata.registry.impl.UiMetadataConfigListener] : Cannot register component ``` with detail ``` org.osgi.service.component.ComponentException: The component name 'Brooklyn UI Metadata' has already been registered by Bundle 375 (org.apache.brooklyn.ui.modularity.brooklyn-ui-metadata-registry) as Component of Class org.apache.brooklyn.ui.modularity.metadata.registry.impl.UiMetadataConfigListener ``` but i'm not convinced this will stick; it may be non-deterministic because i've made previous changes which seemed to fix it, but then they re-occurred, and here i made changes which fixed it then changed some things back and it still seemed to be fixed, but in the end the changes being made don't seem like they should fix the component registration error (3) it also fixes this one which was clearly a debug logging mistake ``` 2021-08-24T12:59:31,245 - ERROR 375 o.a.b.u.m.m.r.i.UiMetadataRegistryImpl [898600076-137202] location ``` (4) better logging for ui module registration in general -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
