Why a plugin is stated as non-compatible just cos a referenced third-party plugin is not compatible?
Hi community. I'm a developer of a Jira plugin that references another third-party plugin through the DynamicImport-Package element in the pom.xml file. This reference is done with resolution:=optional.
In the early days after the Jira 9.12.0 release, the third-party plugin was not yet compatible with such version, and its module was displayed within our plugin as disabled:
and although the rest of our own modules were enabled and functional with the newest Jira version, our plugin installation process was concluded as follows (saying it was not compatible):
It was only after we removed the DynamicImport-Package from the pom.xml file that we got the expected installation result:
My question is, why is our plugin stated as non-compatible when it's actually the third-party plugin that is not compatible especially if it is optional?
1 answer
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.