Databases Reference
In-Depth Information
Releasing your plugin without revision control
If you don't have any revision control, the release process of your plugin involves
some manual steps.
1. Open the
pom.xml
file in your plugin.
2. Change the
<version></version>
parameter to your release version,
that is
1.1
.
3. Save the file.
4. Open a command prompt and go to your plugin location.
5. Run the
atlas-package
command. This command will compile, test,
and build your plugin.
6. After the command is finished, you can find your released plugin in the
target directory in your plugin folder. This should be a
.jar
file, named
for your plugin and version, that is
button-macro-1.1.jar
.
Plugin module types
An Atlassian plugin can specify one or more plugin modules to affect the underlying
Atlassian applications. Plugin modules are elements you can add to your plugin and
which will be translated by the SDK and the application architecture to something
Confluence understands.
We already used the
xhtml-macro
and
web-resource
modules in our first plugin,
but there are many more.
Generic module types
These are module types that are available in every application, not just Confluence.
If you are building a plugin for multiple applications, stick to only these types.
