Apache
/
maven
mirror of https://github.com/apache/maven.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

add missing file 

git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@163904 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Brett Leslie Porter 2005-04-11 16:58:35 +00:00
parent 1c9069c532
commit 02a0040a81
1 changed files with 40 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

40
maven-site/src/site/xdoc/general.fml Normal file
View File

@ -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>