svn commit: r790402 - /maven/plugins/trunk/maven-antrun-plugin/src/site/fml/faq.fml

[pg...@apache.org]

Author: pgier
Date: Wed Jul  1 22:09:31 2009
New Revision: 790402

URL: http://svn.apache.org/viewvc?rev=790402&view=rev
Log:
[MANTRUN-106] Document plugin dependency issue.

Modified:
    maven/plugins/trunk/maven-antrun-plugin/src/site/fml/faq.fml

Modified: maven/plugins/trunk/maven-antrun-plugin/src/site/fml/faq.fml
URL: http://svn.apache.org/viewvc/maven/plugins/trunk/maven-antrun-plugin/src/site/fml/faq.fml?rev=790402&r1=790401&r2=790402&view=diff
==============================================================================
--- maven/plugins/trunk/maven-antrun-plugin/src/site/fml/faq.fml (original)
+++ maven/plugins/trunk/maven-antrun-plugin/src/site/fml/faq.fml Wed Jul  1 22:09:31 2009
@@ -32,6 +32,18 @@
        corresponding Maven expressions.</p>
      </answer>
    </faq>
+   <faq id="Why is antrun not correctly handling my plugin dependency in a multi-module build?">
+     <question>Why is antrun not correctly handling my plugin dependency in a multi-module build?</question>
+     <answer>
+       <p>There is a problem in some versions of Maven (earlier than 3.0-alpha-1) that prevent Maven from correctly resolving
+          plugin dependencies in a multi-module build (MNG-1323).  This means that if you have multiple
+          modules in your project and the antrun plugin declares a different set of dependencies, only the first 
+          declaration found will be used.</p>
+       <p>The workaround for this is to specify the same set of plugin dependencies for all declarations of the
+          antrun plugin.  Another option is to move the plugin dependencies to the project level and set the
+          scope to "provided".  For more information, see MANTRUN-51 and MANTRUN-106.</p>
+     </answer>
+   </faq>
  </part>
 </faqs>