• 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.

      It would be great if all the standard macros that come with Confluence (e.g.

      {children}, , etc) were open sourced and their development made independent from the main Confluence branch. This would provide several advantages:

      1. Smaller fixes/feature requests can be added and released between major releases of Confluence
      2. The need to create similar, but slightly different or slightly enhanced versions of the same macro will be eliminated (eg {no-parents} in the Navigation Macros on CONFEXT vs. {children}

      )
      3. There will be less of a barrier to getting 'trivial' enhancement requests, since the requestors can write the addition themselves.
      4. Non-Atlassian developers can contribute patches and enhancements, allowing Atlassian to focus on adding that latest cool feature to Confluence.

      They can still be included with the standard distributions of Confluence, and installed by default in the WEB-INF/lib directory. But this way, administrators can replace the 'plugins-*.jar' files with updated versions themselves if needed. Currently, you have to have the source code and you'll have to merge it with any Atlassian changes every time a release comes out.

      You may want to establish some basic ground rules for modifying the macros. Eg. all changes should be backwards-compatible. Some well-placed test cases should help with this.

            [CONFSERVER-4353] Open source the standard Confluence plugins and macros

            I concur, it's superb that Atlassian has externalised these macros. You guys have been busy - do you not sleep? I hope the developer community will repay your hard work with some great enhancements to the macros.

            Guy Fraser [Adaptavist.com] added a comment - I concur, it's superb that Atlassian has externalised these macros. You guys have been busy - do you not sleep? I hope the developer community will repay your hard work with some great enhancements to the macros.

            You can probably close this one now. Thanks for that!

            David Peterson added a comment - You can probably close this one now. Thanks for that!

            Ok, 2.1.2 is out the door now, so... Externalising macros...

            hides

            Guy Fraser [Adaptavist.com] added a comment - Ok, 2.1.2 is out the door now, so... Externalising macros... hides

            FYI, we're discussing this internally. We've so far have no objections to the idea in principle, but there are a few practical concerns we have to work out before we can make a final decision. We can't really spare the time to think about them until we've got 1.5 out the door, though, so we'll revisit the question then.

            Charles Miller (Inactive) added a comment - FYI, we're discussing this internally. We've so far have no objections to the idea in principle, but there are a few practical concerns we have to work out before we can make a final decision. We can't really spare the time to think about them until we've got 1.5 out the door, though, so we'll revisit the question then.

              Unassigned Unassigned
              david@randombits.org David Peterson
              Votes:
              8 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: