Conflicting plugins?

[Mizar01]

Hi.
I installed both these plugins:

• camunda-modeler-property-info-plugin from GitHub - mesoneer-ag/camunda-modeler-property-info-plugin: This plugin serves a better overview which properties are set per shape.
• camunda-modeler-plugin-example from GitHub - camunda/camunda-modeler-plugin-example: Plugin example for the Camunda Modeler. Use this as a starting point for creating your own plugins.

When I start camunda, only one of them is really working. It seems that only the first installed is fully working, while the second is listed in the plugins menu, but it does nothing. I’m not sure, anyway, what happens is that only one of them is working, sometimes is the property-plugin, sometimes is the plugin-example.

Is there any way to detect a conflict? apparently in the dev-tools there’s no error related to this problem. It is possible that the style or event catching are conflicting silently?

[daimadoshi85]

Yes, they are conflicting each other because they are registering themselves as plugin with the same name (‘clientPlugin’), you can see it in the project sources on calling ‘registerBpmnJSPlugin’ function (client.js file and PropertyInfoPlugin.js file on module.exports).

I’ll open an issue for camunda-modeler-property-info-plugin, it should change registering name.

[Mizar01]

Thanks. I didn’t notice that.

[philippfromme]

This is indeed a naming conflict. The property info plugin should have a somewhat unique name. I guess, we have to clarify this in the docs.