diff --git a/aspectj/plugin.jelly b/aspectj/plugin.jelly
index 704371e8..6fce85cd 100644
--- a/aspectj/plugin.jelly
+++ b/aspectj/plugin.jelly
@@ -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}"
diff --git a/aspectj/plugin.properties b/aspectj/plugin.properties
index 4e2cb9c4..d35649ed 100644
--- a/aspectj/plugin.properties
+++ b/aspectj/plugin.properties
@@ -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
diff --git a/aspectj/xdocs/changes.xml b/aspectj/xdocs/changes.xml
index 3b6642ca..9bc9725b 100644
--- a/aspectj/xdocs/changes.xml
+++ b/aspectj/xdocs/changes.xml
@@ -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
diff --git a/aspectj/xdocs/properties.xml b/aspectj/xdocs/properties.xml
index bb807aea..ba120d73 100644
--- a/aspectj/xdocs/properties.xml
+++ b/aspectj/xdocs/properties.xml
@@ -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>
 
