[ https://issues.jboss.org/browse/JBIDE-18678?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-18678: ---------------------------------------- {quote} I thought the intent was that if the updatesite containts the usage plugin it will get installed, the third party would simply just exclude it from their updatesite? did that not work ? {quote} It would work if we added this new impl usage plugin as an optional (greedy) dependency to browsersim plugin.xml (and the rest of plugins which use usage) instead of adding that feature requirement. But it still requires to update every JBT component. It seems that if we introduce this new usage impl plugin we can't provide a full backwards compatibility. We have to update usage clients (feature.xml's or plugins.xmls). As alternative we could create an extension point which would disable that dialog. No need to introduce new plugin and no need to change anything in our components which use usage but any plugin would be able to disable usage dialog and the only way to enable usage for the user would be manual enabling via preferences (or uninstalling that plugin which disables the dialog via our new extension point). WDYT? -- This message was sent by Atlassian JIRA (v6.3.11#6341)