Uploaded image for project: 'Confluence Server and Data Center'
  1. Confluence Server and Data Center
  2. CONFSERVER-24432

Define a clear Java API for Confluence plugin developers that won't break when new versions of Confluence are released

    XMLWordPrintable

    Details

    • Feedback Policy:
      We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Description

      NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.

      Writing a Confluence plugin that works across multiple versions of Confluence can be a bit of a challenge. Especially when the Confluence developers accidentally ship changes that break binary compatibility in point releases.

      The JIRA developers recently spent a lot of time in JIRA 5 solving this problem by moving the "blessed" Java API for JIRA into a separate API jar.

      Having a clearly-defined API gives plugin developers the confidence to know which services and methods they can call safely without fear of things changing underneath them.

      It also gives confidence to Confluence developers to know which areas of the code they can change freely, and which areas need to be changed with care to ensure continuing compatibility.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              jclark@atlassian.com Joe Clark
              Votes:
              17 Vote for this issue
              Watchers:
              13 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: