819465bc2e
git-svn-id: https://svn.apache.org/repos/asf/maven/maven-1/plugins/trunk@114119 13f79535-47bb-0310-9956-ffa450edef68
62 lines
2.1 KiB
XML
62 lines
2.1 KiB
XML
<?xml version="1.0"?>
|
|
<document>
|
|
|
|
<properties>
|
|
<title>Maven Caller plugin</title>
|
|
<author email="vmassol@apache.org">Vincent Massol</author>
|
|
</properties>
|
|
|
|
<body>
|
|
<section name="Maven Caller Plug-in">
|
|
<p>
|
|
The Caller plugin is an interface abstraction for goals. It defines
|
|
several Well-Known Goal Interfaces (WKGI). This allows a plugin
|
|
to call another plugin through this Caller plugin. The benefit is
|
|
that it is then possible to rewire the implementation of a WKGI.
|
|
</p>
|
|
<p>
|
|
Here's a typical scenario. Imagine you wish to implement an aspectj
|
|
plugin. This plugin will compile the Java sources using the Aspectj
|
|
compiler. However, the project you wish to use the aspectj plugin on
|
|
is a webapp and thus you will need call the <code>war:war</code>.
|
|
Alas, the <code>war:war</code> goal has a hard-wired call to
|
|
<code>java:compile</code>. What you would like is redirect this call
|
|
to your <code>aspectj:compile</code> goal. The solution: the Caller
|
|
plugin.
|
|
</p>
|
|
<p>
|
|
Here's what you would write. In the war plugin's
|
|
<code>plugin.jelly</code>, you would replace the call to
|
|
</p>
|
|
<source><![CDATA[
|
|
<attainGoal name="java:compile"/>
|
|
]]></source>
|
|
<p>
|
|
by
|
|
</p>
|
|
<source><![CDATA[
|
|
<caller:call goalInterface="compile-java"/>
|
|
]]></source>
|
|
<p>
|
|
Then, in your Aspectj plugin, you would call
|
|
</p>
|
|
<source><![CDATA[
|
|
<caller:set goalInterface="compile-java" goal="aspectj:compile"/>
|
|
]]></source>
|
|
<p>
|
|
Thus, when, as a user you will call the <code>war:war</code>
|
|
goal, your <code>aspectj:compile</code> goal will be called.
|
|
</p>
|
|
<p>
|
|
For more information on the functionality provided by this plugin,
|
|
please see the <a href="goals.html">Goals</a> document.
|
|
</p>
|
|
<p>
|
|
For more information on how to customise the functionality provided
|
|
by this plugin, please see the <a href="properties.html">properties</a>
|
|
document.
|
|
</p>
|
|
</section>
|
|
</body>
|
|
</document>
|