Confluence Data Center 9 compatible version

[genius-worker-ck]

Hello,

the current release v9.0.1 is not compatible with Confluence V9. It can be installed but not enabled.

The log files shows:
ERROR [https-jsse-nio2-443-exec-9] [plugin.osgi.factory.OsgiPluginInstalledHelper] availableForTraversal Cannot determine required plugins, cannot resolve bundle 'com.baloise.confluence.digital-signature'
WARN [https-jsse-nio2-443-exec-9] [osgi.hook.dmz.DmzResolverHook] filterMatches Package com.google.gson is internal and is not available for export to plugin com.baloise.confluence.digital-signature

After some debugging it looks like that according to https://developer.atlassian.com/server/confluence/get-your-apps-ready-for-gray-api-removal/ that the gson dependency is not provided by Confluence 9 via the provided scope. It should be declared as a direct dependency.

Regards,
Carsten

[culmat]

Hello @genius-worker-ck ,
thanks for reaching out. V9.0.1 should fix this issue and be available through the marketplace, see https://marketplace.atlassian.com/apps/1217404/digital-signature/version-history
If you don't see the update option, you can directly download and install the jar file from https://github.com/baloise/digital-signature/tree/gh-pages/9.0.1.

After migration to V9 it seems that in our instance the code page changed and some signatures with special characters where not displayed any more.
I have documented the fix we applied in #118. It relies on the presence of the script runner plugin.

I hope this helps you in getting the plugin to work on your new instance. If not, please let me know and tell me the exact version you are running.

FYI, I'm also working on a cloud version of the plugin, see #99

Best regards,
Matthias

[SplashmasterBee]

I am running into the same issue using v9.0.1 on Confluence 9.2.13 with a Data Center license (single instance).
Trying to re-add the gson library results in the error, that it's internal only and not available for plugins.
From my understanding it needs to be compiled with the dependency's com.google.code.gson scope set to "compile" instead of "provided". Unfortunately I wasn't able to do so myself, since the build fails for me and I don't have the experience to fix that, so I cannot confirm if that's actually the solution.

[genius-worker-ck]

I am running into the same issue using v9.0.1 on Confluence 9.2.13 with a Data Center license (single instance). Trying to re-add the gson library results in the error, that it's internal only and not available for plugins. From my understanding it needs to be compiled with the dependency's com.google.code.gson scope set to "compile" instead of "provided". Unfortunately I wasn't able to do so myself, since the build fails for me and I don't have the experience to fix that, so I cannot confirm if that's actually the solution.

Yes, that is still the issue. What worked for me was the combination of the jar files into one file. As jar files are more or less archives.
This way the gson library could be loaded from the same jar

@SplashmasterBee You can try the following snippet to create the "fat jar"

$ mkdir tmp
$ (cd tmp; unzip -uo ../gson-2.2.2-atlassian-1.jar)
$ (cd tmp; unzip -uo ../digital-signature-9.0.1.jar)
$ jar -cvf digital-signature-9.0.1-with-gson.jar -C tmp .

[SplashmasterBee]

@genius-worker-ck Although it doesn't feel clean, it worked. Thank you.