The App Approval Guidelines for server apps contain several points that require marketplace licensing support for UPM < 2.0.
So the first question is: Do I need to implement this, if I only target Confluence versions that support at least UPM 2.0? This seems to be unnecessary to me but it is not stated clearly.
If it is not necessary, what about this point:
App is runnable without the Licensing API being previously installed: Even though the Licensing API might already be present in your development environment, it may not be previously installed on a customer’s environment. Use the code generation tool to work around this. If it still fails, you may need to consider an alternate deployment model.
To me this looks like that even if I don't support < UPM 2.0, I would need to provide some kind of licensing mechanism. Unfortunately, the 'code generation' links to the 'atlas-create-confluence-plugin-module' with which we could add a LicenseServlet to our project.
The problem with the LicenseServlet is that it is out-dated beyond hope for me.
For example, it depends on "plugin-license-storage-lib" which is not supported anymore. This means, even if I update the LicenseServlet to make it compatible with the Spring scanner ComponentImport, it still won't work because of the missing API. Looking at the pom, it adds the 'plugin-license-storage-plugin' bundle (which seems to be the newer version) but this does not provide the referenced 'ThirdPartyPluginLicenseStorageManager' and the 'AtlassianMarketplaceUriFactory' classes and therefore cannot be injected in the LicenseServlet.
If I need to implement this, why is the code generation this out-dated and more importantly, where can I find a newer version that actually works?
So the first question is: Do I need to implement this, if I only target Confluence versions that support at least UPM 2.0? This seems to be unnecessary to me but it is not stated clearly.
I've contacted the atlassian support directly and was told that it is not necessary. I guess it could be more clearly in the app approval guidelines.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.