Instead of providing username and password data directly to the pom.xml in the plugin configuration, we can configure the server section of settings.xml.
See http://maven.apache.org/settings.html#Servers

The repositories for download and deployment are defined by the repositories and distributionManagement elements of the POM. However, certain settings such as username and password should not be distributed along with the pom.xml. This type of information should exist on the build server in the settings.xml.

See Maven Changes Plugin

We can configure into pom.xml GitHub as issue management :

<project>
  ...
  <issueManagement>
    <system>GitHub</system>
    <url>https://github.com/rails/rails/issues</url>
  </issueManagement>
  ...
</project>

Display the versions of a project with a Maven goal : mantis:display-project-versions.

See the Mantis SOAP API methods :

• mc_project_get_versions
• mc_project_get_released_versions
• mc_project_get_unreleased_versions

Add scm section to pom.xml

See Maven Tips and Tricks: Using GitHub - Step 9 :

Step 9. Open up the pom.xml file of the git-demo project and add the following scm element right before the closing project element. Make sure to substitute your account name for the instances of “tobrien” in the XML snippet shown below:

 <scm>
    <connection>scm:git:[email protected]:tobrien/git-demo.git</connection>
    <url>scm:git:[email protected]:tobrien/git-demo.git</url>
    <developerConnection>scm:git:[email protected]:tobrien/git-demo.git</developerConnection>
  </scm>

JRedmine :: Maven plugin

See Project JRedmine here
See API Doc here

Mojo example : AbstractRedmineMojo

For instance, some versions could be excluded, like the release candidate (x.y-RCn), when adding a version from the project to Mantis.

A regular expression could be used.

Prefix expressions for Mojo's parameters by "mantis."

See Introduction to Plugin Prefix Resolution

Extract :

Specifying a Plugin's Prefix

In order to give users a convenient prefix with which to reference your plugin a prefix must be associated with your plugin when it is built. By default, Maven will make a guess at the plugin-prefix to be used, by removing any instances of "maven" or "plugin" surrounded by dashes in the plugin's artifact ID. The conventional artifact ID formats to use are:

• maven-${prefix}-plugin - for plugins from the Apache Maven project
• ${prefix}-maven-plugin - for plugins from other sources

If your plugin's artifactId fits this pattern, Maven will automatically map your plugin to the correct prefix in the metadata stored within your plugin's groupId path on the repository. However, if you want to customize the prefix used to reference your plugin, you can specify the prefix directly through a configuration parameter on the maven-plugin-plugin in your plugin's POM:

    <project>
      ...
      <build>
        ...
        <plugins>
          ...
          <plugin>
            <artifactId>maven-plugin-plugin</artifactId>
            <version>2.3</version>
            <configuration>
              ...
              <goalPrefix>somePrefix</goalPrefix>
            </configuration>
          </plugin>
        </plugins>
      </build>
    </project>

Do the migration from the changes.xml file managed by the maven-changes-plugin.

It would be nice to pick the versions (releases) in the changes.xml file, and create / update the versions in the project managed by Mantis.
The name of this goal could be mantis:import-versions-from-changes.

See the Mantis SOAP API methods :

• mc_project_version_add
• mc_project_version_update

See the Maven Changes Plugin :

• Alternate Location for the changes.xml File

See :

• Maven Plugin Tool for Annotations
• Maven Plugin Tools
• Using Plugin Tools Java5 Annotations
• Maven Plugin Java 5 Annotations - About Maven Plugin Java 5 Annotations

See : https://commons.apache.org/proper/commons-lang/release-history.html

Add lifecycle mapping metadata into the Maven plugin to help m2e configurator.
Works for m2e 1.1+

See M2E plugin execution not covered and lifecycle mapping metadata provided by maven plugin

See : https://docs.travis-ci.com/user/languages/java/

See : http://mvnrepository.com/artifact/biz.futureware.mantis/mantis-axis-soap-client/1.2.19

If Issue Management is defined in pom.xml, it should be taken into account.
If issueManagement is defined and system = Mantis and url is defined, it is possible to use the url in the goal.
The MavenProject must also be used.

Extract :

This defines the defect tracking system (Bugzilla, TestTrack, ClearQuest, etc) used. Although there is nothing stopping a plugin from using this information for something, its primarily used for generating project documentation.

<project xmlns="http://maven.apache.org/POM/4.0.0"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
                  http://maven.apache.org/xsd/maven-4.0.0.xsd">
  <issueManagement>
    <system>Bugzilla</system>
    <url>http://127.0.0.1/bugzilla/</url>
  </issueManagement>
  ...
</project>

See also :
Example with Redmine : AbstractRedmineMojo.