From 02a0040a8196c5680ed441136f5e61ff0a941f3e Mon Sep 17 00:00:00 2001
From: Brett Leslie Porter <brett@apache.org>
Date: Mon, 11 Apr 2005 16:58:35 +0000
Subject: [PATCH] add missing file

git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@163904 13f79535-47bb-0310-9956-ffa450edef68
---
 maven-site/src/site/xdoc/general.fml | 40 ++++++++++++++++++++++++++++
 1 file changed, 40 insertions(+)
 create mode 100644 maven-site/src/site/xdoc/general.fml

diff --git a/maven-site/src/site/xdoc/general.fml b/maven-site/src/site/xdoc/general.fml
new file mode 100644
index 0000000000..373c00cbab
--- /dev/null
+++ b/maven-site/src/site/xdoc/general.fml
@@ -0,0 +1,40 @@
+<?xml version="1.0"?>
+<faqs id="General FAQ">
+  <part id="General">
+    <faq id="scripting-languages">
+      <question>What plugin languages will Maven 2.0 support? What about [insert language here]?</question>
+      <answer>
+        <p>
+          As of the Technology Preview, Maven supports pure Java and Marmalade. Java is the preferred language
+          for it's familiarity and speed, while Marmalade is preferred for porting Maven 1.x plugins, and writing
+          plugins based on Ant tasks.
+        </p>
+        <p>
+          In alpha-2, Beanshell support is planned. We currently view this as the best candidate to be the primary
+          plugin scripting language in Maven 2.0.
+        </p>
+        <p>
+          We get asked a lot whether Maven 2.0 will support other languages, in particular Groovy.
+          We will allow the use of Groovy - and virtually any other scripting
+          language if there is demand, or someone can commit a small amount of time to implementing a
+          factory for it.
+        </p>
+        <p>
+          We would recommend waiting for Groovy to have a 1.0 release so the API
+          (and language!) is stable. What we will not be doing is actively
+          supporting it (in terms of answering questions about how to use it)
+          like we currently do for Jelly in Maven 1.x.
+        </p>
+        <p>
+          Beanshell is more mature, and we want a language that users will find
+          answers for when they look, and that when they find bugs, it is
+          clearly defined where they actually are.
+        </p>
+        <p>
+          We may consider emphasising a different language if there are compelling technical reasons
+          for doing so - if you have a suggestion, feel free to contact the development list.
+        </p>
+      </answer>
+    </faq>
+  </part>
+</faqs>