Databases Reference
In-Depth Information
</nonProxyHosts>
</proxy>
</proxies>
</settings>
3. Save the file.
With a normal Maven installation, or if you have multiple installations,
mvn
would
be available via your command prompt. To ensure you use the Atlassian provided
version, Maven uses
atlas-mvn
instead.
The pom.xml file
In the root of your plugin, there is a
pom.xml
file; this file is the core of a project's
configuration in Maven. In this file, you can define dependencies on other libraries
and specify which Confluence version you want to run, but it also holds the name
and description of your plugin.
The
pom.xml
file is what is being used when you start your plugin with
atlas-run
.
The plugin descriptor
Every plugin must have a plugin descriptor file. The file,
atlassian-plugin.xml
,
describes your plugin to the target application. The Atlassian SDK generates
the
atlassian-plugin.xml
file when you create your plugin for the first time.
The descriptor is also updated when you use
atlassian-create-confluence-
plugin-module
to add a new module.
At some point during the development of you plugin, you will have to update
the file manually, so it's a good idea to have a bit of understanding as to what
is in the plugin descriptor. The plugin descriptor is located in the directory
<plugin_home>/src/main/resources/
.
A very minimal plugin descriptor's built looks as follows:
<atlassian-plugin key="${project.groupId}.${project.artifactId}"
name="${project.name}" plugins-version="2">
<plugin-info>
<description>${project.description}</description>
<version>${project.version}</version>
<vendor name="${project.organization.name}"
url="${project.organization.url}" />
</plugin-info>
</atlassian-plugin>
