Uploaded image for project: 'Atlassian Marketplace'
  1. Atlassian Marketplace
  2. AMKT-3846

Deployable add-ons with a plugin key historically different to the AMKT add-on key can no longer be uploaded

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Not a bug
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      Reported by Matthew Jensen, while trying to upload a new version of the Confluence Roadmap Plugin.

      Upon trying to upload a new version of the plugin, he received a new validation error:

      Add-on key in plugin descriptor (com.atlassian.plugins.confluence-roadmap-plugin) did not match existing add-on (com.atlassian.confluence.plugins.confluence-roadmap-plugin)

      The plugin key in the jar had never changed. The problem was that when the marketplace listing was first created, the plugin key and add-on key were allowed to be different.

      It took us a little while to work out what the exact problem was, so this may be confusing for any external developers in the same situation.

      If this new validation really must exist, can we go through and identify anyone else who might be affected and either automatically change their add-on key for them, or I can contact them and let them know what to do?

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              jclark Joseph Clark
            • Votes:
              0 Vote for this issue
              Watchers:
              12 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Who's Looking?