You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by pg...@apache.org on 2010/02/23 23:22:13 UTC

svn commit: r915550 - /maven/plugins/trunk/maven-antrun-plugin/src/site/apt/usage.apt.vm

Author: pgier
Date: Tue Feb 23 22:22:13 2010
New Revision: 915550

URL: http://svn.apache.org/viewvc?rev=915550&view=rev
Log:
[MANTRUN-128] Update docs to reflect deprecation of sourceRoot and testSourceRoot params.

Modified:
    maven/plugins/trunk/maven-antrun-plugin/src/site/apt/usage.apt.vm

Modified: maven/plugins/trunk/maven-antrun-plugin/src/site/apt/usage.apt.vm
URL: http://svn.apache.org/viewvc/maven/plugins/trunk/maven-antrun-plugin/src/site/apt/usage.apt.vm?rev=915550&r1=915549&r2=915550&view=diff
==============================================================================
--- maven/plugins/trunk/maven-antrun-plugin/src/site/apt/usage.apt.vm (original)
+++ maven/plugins/trunk/maven-antrun-plugin/src/site/apt/usage.apt.vm Tue Feb 23 22:22:13 2010
@@ -97,60 +97,12 @@
 [...]
 ------
 
-  Below you can see how to indicate that Ant has generated some more java
-  source that needs to be included in the compilation phase. Note that the
-  compile phase follows the <<<generate-sources>>> phase in the lifecycle.
+* Additional source directories
 
-------
-<project>
-  [...]
-  <build>
-    <plugins>
-      [...]
-      <plugin>
-        <artifactId>maven-antrun-plugin</artifactId>
-        <version>${project.version}</version>
-        <executions>
-          <execution>
-            <phase>generate-sources</phase>
-            <configuration>
-              <tasks>
-
-                <!--
-                  Place any Ant task here. You can add anything
-                  you can add between <target> and </target> in a
-                  build.xml.
-                -->
-
-              </tasks>
-              <sourceRoot>
-                \${project.build.directory}/generated-sources/main/java
-              </sourceRoot>
-              <testSourceRoot>
-                \${project.build.directory}/generated-sources/test/java
-              </testSourceRoot>
-            </configuration>
-            <goals>
-              <goal>run</goal>
-            </goals>
-          </execution>
-        </executions>
-      </plugin>
-    </plugins>
-  </build>
-  [...]
-</project>
-------
-
-  Of course, you can put whatever folder you prefer. The folders in the example
-  above are handy because they are deleted when you <<<clean>>> since they are in
-  the build directory (which is, by default, "target").
-
-  <<<\<sourceRoot/\>>>> adds a single folder to the list of folders that get
-  compiled with the program source code (<<<compile>>>).
-
-  <<<\<testSourceRoot/\>>>> adds a single folder to the list of folders that get
-  compiled with the test source code (<<<test-compile>>>).
+  If your ant tasks generate additional source code that needs to be added 
+  to the build, you can use the 
+  {{{http://mojo.codehaus.org/build-helper-maven-plugin/}build-helper-maven-plugin}}.  
+  The sourceRoot and testSourceRoot options of the antrun plugin have been deprecated.
 
 * Using maven properties