Apache Maven 3 Cookbook

Extending Apache Maven
myProperties is now available for use in your MOJO and its values are read during
execution from the POM file.
For a plugin that needs to be executed from the console, a short command
line is preferable. Here's a quick recap of how we executed the plugin from
the command line:
$ mvn net.srirangan.packt.maven:maven-plug101-plugin:1.0-
SNAPSHOT:helloworld
A little too long, don't you think? Remember how we ran the Jetty server through the
plugin in earlier chapters?
$ mvn jetty:run
Short and sweet. How do we do the same, that is, shorten the command-line call with
our plugin? (We're off to a good start, so the process of shortening won't be
very hard.)
Firstly, we have the latest version of the plugin installed in our local
repository. That is what we're trying to execute. We can directly do
away with the version number, and our command becomes:
$ mvn net.srirangan.packt.maven:maven-plug101-
plugin:helloworld
We also followed the Maven plugin naming conventions, that is,
maven-{plugin_name}-plugin. This allows us to shorten it a bit further.
Finally, add the plugin's groupId as a pluginGroup in the Maven settings
file (settings.xml):
net.srirangan.packt.maven
We should now be able to run the plugin using a short command in
the console:
$ mvn plug101:helloworld
5. Here's how you integrate the Apache Maven plugin with the project build lifecycle:
You will need to modify the project's POM file and include the executions element
in the build and plugin description. The following code consists of the integration
of the plugin with the compile phase:
194