Custom server Add-on key format

[Raimundas Juska]

Hi,

I have developed and published some Cloud apps to the marketplace. At that moment I was not aware of the add-on key proper format (reverse domain name notation). So these Cloud app keys are not in format groupId.artifactId

I have now finished Server versions of the same apps, which uses reverse domain name notation. However, I can not use same listing for these two versions because of the key differences.

What are my options now? I have tried changing <atlassian-plugin key="${atlassian.plugin.key}"> to <atlassian-plugin key="some.static.cloud.app.key"> as a solution, but this doesn't seem to work, with builds failing.

[Aleksandr Zuevich · Accepted solution]

Hi,

Have you changed the key in <atlassian-plugin key="some.static.cloud.app.key"> only?

Don't forget to change also in jira maven plugin instruction:

<Atlassian-Plugin-Key>${atlassian.plugin.key}</Atlassian-Plugin-Key>

Or better change this line:

<atlassian.plugin.key>${project.groupId}.${project.artifactId}</atlassian.plugin.key>

to this:

<atlassian.plugin.key>some.static.cloud.app.key</atlassian.plugin.key>

[Raimundas Juska]

Thank you! Seems to be working now.

However, is this an acceptable practice with Atlassian plugin key not being the same as Maven's ${project.groupId}.${project.artifactId}?