Applied MPASPECTJ-9

git-svn-id: https://svn.apache.org/repos/asf/maven/maven-1/plugins/trunk@115216 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
vmassol 2004-05-10 18:23:05 +00:00
parent f5d80cbc7d
commit 3ca4145fae
4 changed files with 42 additions and 2 deletions

View File

@ -95,8 +95,10 @@
<j:if test="${shouldWeave == 'true'}">
<ant:iajc fork="false"
incremental="{maven.aspectj.incremental}"
<ant:iajc
fork="${maven.aspectj.fork}"
maxmem="${maven.aspectj.maxmem}"
incremental="${maven.aspectj.incremental}"
destDir="${maven.build.dest}"
sourceRootCopyFilter="${maven.aspectj.sourceRootCopyFilter}"
debug="${maven.aspectj.debug}"

View File

@ -34,3 +34,14 @@ maven.aspectj.verbose = false
# incremental mode: Build once, then recompile only required source files
# when user provides input.
maven.aspectj.incremental = false
# Run process in another VM. This gets the forking classpath either explicitly
# from a forkclasspath entry or by searching the task or system/Ant classpath
# for the first readable file with a name of the form aspectj{-}tools{.*}.jar.
# When forking you can specify the amount of memory used with maxmem. Fork cannot
# be used in incremental mode, unless using a tag file.
maven.aspectj.fork = false
# The maximum memory to use for the new VM when fork is true. Values should
# have the same form as accepted by the VM, e.g., "128m".
maven.aspectj.maxmem = 128m

View File

@ -28,6 +28,10 @@
</properties>
<body>
<release version="3.0" date="in CVS">
<action dev="vmassol" type="add" issue="MPASPECTJ-9" due-to="Carlos Sanchez" due-to-email="carlossg@users.sourceforge.net">
Added new <code>maven.aspectj.fork</code> and
<code>maven.aspectj.maxmem</code> properties.
</action>
<action dev="vmassol" type="update" issue="MPASPECTJ-8" due-to="Carlos Sanchez" due-to-email="carlossg@users.sourceforge.net">
Another almost complete rewrite of the plugin. The plugin is now
using AspectJ 1.2rc1 and allows weaving at class level (instead of

View File

@ -84,6 +84,29 @@
</td>
</tr>
<tr>
<td>maven.aspectj.fork</td>
<td>Yes</td>
<td>
Run process in another VM. This gets the forking classpath either explicitly
from a forkclasspath entry or by searching the task or system/Ant classpath
for the first readable file with a name of the form aspectj{-}tools{.*}.jar.
When forking you can specify the amount of memory used with maxmem. Fork cannot
be used in incremental mode, unless using a tag file.<br/>
Default <code>false</code>
</td>
</tr>
<tr>
<td>maven.aspectj.maxmem</td>
<td>Yes</td>
<td>
The maximum memory to use for the new VM when fork is true. Values should have
the same form as accepted by the VM, e.g., "128m".
Default <code>128m</code>
</td>
</tr>
</table>
</section>