When we created the Confluence and JIRA Plugin Development Kits our goal was to include absolutely everything someone would need to build a plugin in one download. We tried to imagine someone writing code on a plane, without net access. (In fact, this is how Mike tends to write his best plugins, but that’s another story.)
So we included all of the dependencies (all 60mb of them). We included the appropriate version of the javadocs (even thought they’re all available on the web). We included templates and examples.
However, much of that isn’t really necessary for those someone who isn’t on a plane. The docs are available without downloading. The examples can be read on the web or you can download just the one you need. And thanks to Maven, all of the project dependencies can be handled automatically in a way that doesn’t duplicate the libraries that don’t change from version to version.
So to make it things simpler, I’ve uploaded the bare minimum requirements for getting a plugin project going:
- I’ve added a copy of the project templates (JIRA, Confluence).
- I’ve also committed a copy of the project.xml for JIRA and Confluence. I’ve included at least the final release of each major version (back to 3.1 and 1.4, respectively).
Download these files and change your plugin’s project.xml to extend from the version you want. You’ll be able to build and test your plugin against each version of JIRA or Confluence just by changing one line of XML. And Maven will intelligently handle all of the dependencies, downloading the ones you need and and storing them in your local Maven repository.
The official, full-sized Plugin Development Kits aren’t going away. But this is an alternative, lighter-weight way of doing plugin development. And it should make version-compatibility testing somewhat easier. I hope you find these additions useful.