vmassol
becb5d8d0b
- The next step is probably to add support for executing java applications using the different AW bootstrapping mechanisms git-svn-id: https://svn.apache.org/repos/asf/maven/maven-1/plugins/trunk@114510 13f79535-47bb-0310-9956-ffa450edef68
137 lines
4.2 KiB
XML
137 lines
4.2 KiB
XML
<?xml version="1.0" encoding="UTF-8"?>
|
|
|
|
<document>
|
|
<properties>
|
|
<title>AspectWerkz properties</title>
|
|
<author email="vmassol@apache.org">Vincent Massol</author>
|
|
</properties>
|
|
<body>
|
|
<section name="AspectWerkz generic properties">
|
|
<table>
|
|
<tr>
|
|
<th>Property</th>
|
|
<th>Optional?</th>
|
|
<th>Description</th>
|
|
</tr>
|
|
<tr>
|
|
<td>maven.aspectwerkz.mode</td>
|
|
<td>Yes</td>
|
|
<td>
|
|
AW supports 2 types of Aspects/Advice/Pointcuts definition:
|
|
<ul>
|
|
<li>
|
|
<strong>xmldef</strong>: Advice are defined as extending
|
|
*Advice classes (BeforeAdvice, AroundAdvice, etc). Custom
|
|
javadoc attributes can be used to link code to weave with
|
|
advices.
|
|
</li>
|
|
<li>
|
|
<strong>attribdef</strong>: Advices and pcds are defined
|
|
purely using custom javadoc attributes (@Execute, @Aspect,
|
|
etc).
|
|
</li>
|
|
</ul>
|
|
You need to tell the plugin how you have defined your AW
|
|
Aspects/Advices/Pointcuts. The 2 valid values are
|
|
<code>xmldef</code> and <code>attribdef</code>.
|
|
The default value is <code>attribdef</code>.
|
|
</td>
|
|
</tr>
|
|
<tr>
|
|
<td>maven.aspectwerkz.src.dir</td>
|
|
<td>Yes</td>
|
|
<td>
|
|
Location of aspect sources. Default location is
|
|
<code>${basedir}/src/main</code>.
|
|
</td>
|
|
</tr>
|
|
<tr>
|
|
<td>maven.aspectwerkz.build.dir</td>
|
|
<td>Yes</td>
|
|
<td>
|
|
Location where weaved classes will be generated. Default to
|
|
<code>${maven.build.dest}</code>.
|
|
</td>
|
|
</tr>
|
|
<tr>
|
|
<td>maven.aspectwerkz.definition.validate</td>
|
|
<td>Yes</td>
|
|
<td>
|
|
Decide whether definition validation is turned on or off.
|
|
Defaults to <code>false</code>.
|
|
</td>
|
|
</tr>
|
|
<tr>
|
|
<td>maven.aspectwerkz.verbose</td>
|
|
<td>Yes</td>
|
|
<td>
|
|
Decide whether to use verbose output or not during execution of
|
|
this plugin's goals. Defaults to <code>false</code>.
|
|
</td>
|
|
</tr>
|
|
</table>
|
|
</section>
|
|
|
|
<section name="AspectWerkz properties specific to 'attribdef' mode">
|
|
<table>
|
|
<tr>
|
|
<th>Property</th>
|
|
<th>Optional?</th>
|
|
<th>Description</th>
|
|
</tr>
|
|
<tr>
|
|
<td>maven.aspectwerkz.definition.file.src</td>
|
|
<td>Yes</td>
|
|
<td>
|
|
Location of the XML definition file. Default to
|
|
<code>${basedir}/conf/aspectwerkz.xml</code>.
|
|
</td>
|
|
</tr>
|
|
</table>
|
|
</section>
|
|
|
|
<section name="AspectWerkz properties specific to 'xmldef' mode">
|
|
<table>
|
|
<tr>
|
|
<th>Property</th>
|
|
<th>Optional?</th>
|
|
<th>Description</th>
|
|
</tr>
|
|
<tr>
|
|
<td>maven.aspectwerkz.definition.file.build</td>
|
|
<td>Yes</td>
|
|
<td>
|
|
Location of the AW XML definition file that will be created by the
|
|
attribute compilation (when calling the
|
|
<code>aspectwerkz:attributec</code> goal). This is only used in
|
|
<code>xmldef</code> mode. Defaults to
|
|
<code>${maven.build.dir}/aspectwerkz.xml</code>.
|
|
</td>
|
|
</tr>
|
|
<tr>
|
|
<td>maven.aspectwerkz.definition.file.merge</td>
|
|
<td>Yes</td>
|
|
<td>
|
|
Definition file to be merged with the main definition file.
|
|
This property is not defined by default.
|
|
</td>
|
|
</tr>
|
|
<tr>
|
|
<td>maven.aspectwerkz.uuid</td>
|
|
<td>Yes</td>
|
|
<td>
|
|
UUID to use. If not specified a default one will be
|
|
automatically generated. This property is not defined by default.
|
|
</td>
|
|
</tr>
|
|
<tr>
|
|
<td>maven.aspectwerkz.transform.filter</td>
|
|
<td>Yes</td>
|
|
<td>
|
|
TODO: explain property here. Defaults to <code>no</code>.
|
|
</td>
|
|
</tr>
|
|
</table>
|
|
</section>
|
|
</body>
|
|
</document> |