Goals of the plugin

Here is the description of the plugin's goals.

Goals

GoalDescription
checkMaximoHome == INTERNAL GOAL ==

This goal is used by other goals of the plugin and should not be called directly.

It is used to validate that the supplied value for the property maximo.home is a valid path for a Maximo installation.
maximo:copy-deps To copy only the specially marked dependencies of a sub-project, ones with an attribute named like the [pom.artifactId]-deploy and with a value 'true'. Other project properties can be set under each dependency in order to control its name and destination when it gets copied. The property list goes as follow:

An example of a dependency declaration using those properties can be found at the bottom of this document.
maximo:createInstructions

This goal is used to create installation instructions for your component or hotfix package. The instructions are produced from XDoc documents into a pdf using the maven-pdf-plugin. See the Usage document in section: Producing Installation instruction PDF for more details.

maximo:dev-deploy

This goal is used to deploy all the Maximo files to your local Maximo server. The location of the actual Maximo installation is indicated in the property: maximo.home. The list of files to be copied is given by the content properties. See the sectionb Code Patch content for more information on the code patch files that gets deployed with this goal.

maximo:dev-undeploy This goal removes a deployment made using the dev-deploy goal. It will remove all copied files from the Maximo installation and replace the old ones backed-up while deploying.

ATTENTION: All the files backed-up from the last dev-deploy will be replaced on your Maximo installation. So if multiple dev-deploy are done, it may not be the original files that gets replaced but the last one that was backed-up.
devdeploy-init == INTERNAL GOAL ==

This goal is used by other goals of the plugin and should not be called directly.

init-env == INTERNAL GOAL ==

This goal is used by other goals of the plugin and should not be called directly.

init-patch == INTERNAL GOAL ==

This goal is used by other goals of the plugin and should not be called directly.

isBackupDirAvailable == INTERNAL GOAL ==

This goal is used by other goals of the plugin and should not be called directly.

maximo:make-codepatch This goal creates the Maximo codepatch assembly for the project. All the files selected for the code patch by the multiple properties available for the purpose, will get copied to the code patch assembly directory. This directory is pointed out by the maximo.patch.code.patch.assembly.dir property. All Code-patch content control properties can be found in the
maximo:make-dist This is the default goal of the plugin. It creates a deliverable package in the form of a zip file. The name of the package as well as its content is partially controlled by some of the plugin properties. Custom Jelly code can also be used to enrich the distribution with files that are not handled by using plugin properties.

Details about the properties are found in the properties page.

Project.xml code extract

This is an example on how to set at the project level the output directory for libraries (maven dependencies) that gets copied by the copy-deps goal of this plugin.

In the following extract, the directory lib is used as the default subdirectory for the publishing of marked dependencies. 


... 
    </versions>    

    <properties>
      <jar.dependency.dist.dir>lib</jar.dependency.dist.dir>
    </properties>
    
    <dependencies>
      <dependency>
...

This other extract shows how to configure the plugin so that a dependency is deployed in a subdirectory and using a different name than the one used by Maven (jarname-version).

NOTE: In the following example, the project ID is: myproject. 


...
<dependency>
  <groupId>commons-logging</groupId>
  <artifactId>commons-logging</artifactId>
  <version>1.0.4</version>
  <url>http://jakarta.apache.org/commons/logging.html</url>
  <properties>
    <myproject.deploy>true</myproject.deploy>
    <jar.manifest.classpath>true</jar.manifest.classpath>
    <jar.dependency.dist.dir>lib/3rdparty</jar.dependency.dist.dir>
    <jar.dependency.dist.name>commons-logging.jar</jar.dependency.dist.name>
  </properties>
</dependency>
...