EXTSCRIPT-157: prepare and improve the site documentation for the 1.0.2 and 1.0.3 release announcments in the users list.

improving docs adding 1.0.3 section to the download links

git-svn-id: https://svn.apache.org/repos/asf/myfaces/extensions/scripting/trunk@1303008 13f79535-47bb-0310-9956-ffa450edef68
diff --git a/extscript-core-root/extscript-core/src/main/scala/org/apache/myfaces/extensions/scripting/core/engine/compiler/ScalaCompiler.scala b/extscript-core-root/extscript-core/src/main/scala/org/apache/myfaces/extensions/scripting/core/engine/compiler/ScalaCompiler.scala
index 4915b53..3c59352 100644
--- a/extscript-core-root/extscript-core/src/main/scala/org/apache/myfaces/extensions/scripting/core/engine/compiler/ScalaCompiler.scala
+++ b/extscript-core-root/extscript-core/src/main/scala/org/apache/myfaces/extensions/scripting/core/engine/compiler/ScalaCompiler.scala
@@ -45,7 +45,7 @@
     targetPath.mkdirs();
     val sourceFiles = FileUtils.fetchSourceFiles(sourcePath, "*.scala")
     var sourceFileNames = List[String]()
-    for (sourceFile: File <- sourceFiles)
+    for (sourceFile:File <- sourceFiles)
     {
       sourceFileNames = sourceFileNames ::: List(sourceFile.getAbsolutePath())
     }
@@ -56,7 +56,7 @@
     var cp: String = System.getProperty("java.class.path")
 
 
-    if(!cp.contains("scala")) {
+    if(!cp.contains("scala")) { //probably a war container
       val classesDir = ClassUtils.getContextClassLoader().getResource("./").getFile();
 
       val libDir = classesDir+".."+File.separator+"lib"
@@ -65,7 +65,7 @@
       finalPath.append(cp)
       finalPath.append(File.pathSeparator)
       finalPath.append(classesDir)
-      for(singleLib:File<-libs){
+      for(singleLib:File <- libs){
         finalPath.append(File.pathSeparator)
         finalPath.append(singleLib.getAbsolutePath)
       }
diff --git a/src/site/apt/download.apt b/src/site/apt/download.apt
index 093470b..d704e7d 100644
--- a/src/site/apt/download.apt
+++ b/src/site/apt/download.apt
@@ -19,7 +19,18 @@
 
 Download Apache MyFaces Extension Scripting
 
- Apache MyFaces Extension Scripting now has a 1.0.2 bugfix release which reenables compatibility with newer MyFaces 
+
+ Apache MyFaces 1.0.3 is the newest version (not yet released). Significant changes have been made
+ to Ext-Scripting 1.0.3, a general refactoring for maintainability was performed and basic
+ Scala support added.
+ Note, this is the first release, which is java6 and MyFaces 2.1.x only. For older versions of MyFaces
+ and Java 5, download Ext-Scripting 1.0.2.
+
+ Download Links and Release Notes will follow soon.
+
+ Ext-Scripting 1.0.2
+
+ Apache MyFaces Extension Scripting now has a 1.0.2 bugfix release which reenables compatibility with newer MyFaces
  versions:
  Apache MyFaces is distributed as jar archives for inclusion and as war archives for the
  examples.
diff --git a/src/site/xdoc/configentries.xml b/src/site/xdoc/configentries.xml
index 28d68e3..65f4ef8 100644
--- a/src/site/xdoc/configentries.xml
+++ b/src/site/xdoc/configentries.xml
@@ -58,6 +58,15 @@
                     </td>
                 </tr>
                 <tr>
+                    <td>org.apache.myfaces.extensions.scripting.scala.LOADER_PATHS</td>
+                    <td>NO</td>
+                    <td>comma separate list of paths</td>
+                    <td>Additional comma separated loader paths to allow direct editing of scala files on the sources
+                        directory instead of editing in the deployment dir /WEB-INF/scala
+                        <b>Note this functionality is enabled only in ext-script 1.0.3 or newer</b>
+                    </td>
+                </tr>
+                <tr>
                     <td>org.apache.myfaces.extensions.scripting.java.LOADER_PATHS</td>
                     <td>NO</td>
                     <td>comma separate list of paths</td>
diff --git a/src/site/xdoc/exampleconfig.xml b/src/site/xdoc/exampleconfig.xml
index abc2c3c..8a2189e 100644
--- a/src/site/xdoc/exampleconfig.xml
+++ b/src/site/xdoc/exampleconfig.xml
@@ -120,6 +120,18 @@
             /Users/werpu2/development/workspace/extensions-scripting3/examples/myfaces20-example/src/main/webapp/WEB-INF/java
         </param-value>
     </context-param>
+    <!-- ======================================================================================
+            Loader path for Scala files
+         ====================================================================================== -->
+    <context-param>
+        <description>Additional comma separated loader paths to allow direct editing on the sources directory instead
+            of the deployment dir
+        </description>
+        <param-name>org.apache.myfaces.extensions.scripting.scala.LOADER_PATHS</param-name>
+        <param-value>
+            /Users/werpu2/development/workspace/extensions-scripting3/examples/myfaces20-example/src/main/webapp/WEB-INF/scala
+        </param-value>
+    </context-param>
 
     <!-- ======================================================================================
             Optional Loader Paths for resource files
diff --git a/src/site/xdoc/installation.xml b/src/site/xdoc/installation.xml
index 0d4567e..a498963 100644
--- a/src/site/xdoc/installation.xml
+++ b/src/site/xdoc/installation.xml
@@ -88,7 +88,7 @@
 
         <section name="Checkout and Build">
             <p>
-                While Ext-Scripting is already in beta stage, the best way to get started
+                While Ext-Scripting is already in stable stage, the best way to get started
                 is probably to checkout and build ext-scripting yourself from the latest codebase.
                 All other installation steps will have this step as prerequisite if you want to
                 use the latest codebase instead of one of the beta releases!
@@ -177,7 +177,7 @@
      </dependency>]]></source>
             </subsection>
 
-    
+
             <subsection name="Manual Setup">
                 <p>If you do not like Maven or you prefer a manual setup, Ext-Scripting provides convenient meta bundles.
                     A manual setup
@@ -276,6 +276,10 @@
                         <b>org.apache.myfaces.extensions.scripting.java.LOADER_PATHS</b>
                         does the same for Java sources..
                     </li>
+                    <li>
+                        <b>org.apache.myfaces.extensions.scripting.scala.LOADER_PATHS</b>
+                        does the same for Java Scala (Ext-Scripting 1.0.3 or newer)...
+                    </li>
                 </ul>
 
                 <h4>Dynamic resource reloading</h4>
diff --git a/src/site/xdoc/usersguide.xml b/src/site/xdoc/usersguide.xml
index c2ce7c6..f43215d 100644
--- a/src/site/xdoc/usersguide.xml
+++ b/src/site/xdoc/usersguide.xml
@@ -46,7 +46,8 @@
                 means, it tries to reduce the number of needed server restarts to the lowest possible minimum which is
                 achievable within the boundaries of Java and JSF.
                 Also it is not yet fully integrated into the bigger application servers, testing only currently is
-                done for Apache Tomcat and Jetty.
+                done for Apache Tomcat and Jetty. Scala due to the nature of its compiler interface, definitely only
+                will work in an expanded embedded WAR environment, not in an EAR environment.
             </p>
             <p>
                 You won't get a zero restart configuration, Extension-Scripting tries not to be perfect in this regard,
@@ -60,13 +61,8 @@
                 the basics right and then in subsequent releases to add additional scripting languages support.
             </p>
             <p>
-                As is, every scripting language which can compile against the JVM can be supported, currently there is
-                no
-                support for the scripting language API of Java 6. The reason simply is that the API is too limiting for
-                now
-                in what Ext-Scripting tries to achieve. But future extensions like JSR 292 once available might be used
-                to
-                reduce the number of restarts needed.
+                As is, every scripting language which can compile against the JVM can be supported. Purely interpreted
+                languages are not supported.
             </p>
             <p>
                 For now we cannot recommend to use Ext-Scripting in a production environment for live patches, although