This is an automated email from the ASF dual-hosted git repository.
elharo pushed a commit to branch elharo-patch-2
in repository https://gitbox.apache.org/repos/asf/maven-antrun-plugin.git
commit 5fc629bed2ba0e9d2c7366168dcf3fcf696ae9ab
Author: Elliotte Rusty Harold <elh...@users.noreply.github.com>
AuthorDate: Sun Apr 5 16:17:41 2020 -0400
[MNGSITE-393] assume Maven 3.0 or later
@eolivelli
---
src/site/fml/faq.fml | 12 ------------
1 file changed, 12 deletions(-)
diff --git a/src/site/fml/faq.fml b/src/site/fml/faq.fml
index 0ae6c55..8205d57 100644
--- a/src/site/fml/faq.fml
+++ b/src/site/fml/faq.fml
@@ -35,18 +35,6 @@ under the License.
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>
