Hi there,
enclosed please find the suggested changes for various files for the
release version of BSF 2.4.0. The only change on Java code was in
updating the value of the "version" field in the BSFManager class, such
that getVersion() now returns a newer version number than the RCs did
(also enhanced the documentation of the version string encoding).
If no one objects I would check them in later today:
Regards,
---rony
Index: xdocs/problems.xml
===================================================================
--- xdocs/problems.xml (revision 449215)
+++ xdocs/problems.xml (working copy)
@@ -19,7 +19,7 @@
you may encounter - these are just some suggestions to point
you in the right direction.
</p>
-
+
<subsection name="Read the Manual">
<p>
The first step to take when you have a problem with BSF is to read
@@ -50,7 +50,7 @@
else may have already encountered this problem, and perhaps it has
been fixed. The next step, therefore, may be to try a nightly build
of BSF to see if the problem has been fixed. Nightly builds for BSF
- are available from the
+ are available from the
<a href="http://www.apache.org/dist/jakarta/jakarta-bsf/nightly/";>
Jakarta web site</a>. While BSF nightly builds are typically quite
stable and are used by
@@ -65,7 +65,7 @@
optional task.
</p>
</subsection>
-
+
<subsection name="Has It Been Reported?">
<p>
If the current nightly build doesn't resolve your problem, it is
@@ -85,7 +85,7 @@
of this bug.
</p>
</subsection>
-
+
<subsection name="Filing a Bug Report">
<p>
By this time, you may have decided that there is an unreported
@@ -101,9 +101,9 @@
correct values for the various inputs when creating the bug, such
as which version of BSF you are running, and on which platform,
etc. Once the bug is created, you can also add attachments to
- the bug report.
+ the bug report.
</p>
- <p>
+ <p>
What information should you include in your bug report? The
easiest bugs to fix are those that are most easily reproducible,
so it is really helpful if you can produce a small test case that
@@ -134,21 +134,21 @@
These are just a different type of bug report. If you look in the
bug database, you will see that one of the severity settings for
a bug is "Enhancement". Just fill the bug report in,
- set the severity of the bug to "Enhancement", and
+ set the severity of the bug to "Enhancement", and
state in the description how you would like to have BSF enhanced.
Again, you should first check whether there are any existing
enhancment requests that cover your needs. If so, just add your
vote to these.
</p>
</subsection>
-
+
<subsection name="Fixing the Bug">
<p>
If you aren't satisfied with just filing a bug report, you can
try to find the cause of the problem and provide a fix yourself.
The best way to do that is by working with the latest code from
CVS.
Alternatively, you can work with the source code available from the
- <a
href="http://jakarta.apache.org/builds/jakarta-bsf/release/v2.3/src/";>
+ <a
href="http://jakarta.apache.org/builds/jakarta-bsf/release/v2.4/src/";>
source distributions</a>. If you
are going to tackle the problem at this level, you may want to
discuss some details first on the <nobr><code>bsf-dev</code></nobr>
@@ -175,15 +175,15 @@
<font face="verdana" size="-1">
cvs diff -u Javac.java > javac.diffs<br></br><br></br>
</font>
-
- Note: You should give your patch files meaningful names.
+
+ Note: You should give your patch files meaningful names.
This makes it easier for developers who need to apply a number
of different patch files.
</p>
</subsection>
-
-
+
+
</section>
-
+
</body>
</document>
Index: xdocs/index.xml
===================================================================
--- xdocs/index.xml (revision 449215)
+++ xdocs/index.xml (working copy)
@@ -118,17 +118,27 @@
<!--
<a href="http://www.apache.org/dist/jakarta/jakarta-bsf/release/v2.3/bin/";></a>
-->
- Download the binary release</li>
+ <a
href="http://www.apache.org/dist/jakarta/jakarta-bsf/release/v2.4/bin/";>
+ Download the binary release
+ </a>
+ </li>
+
<li>
<!--
<a href="http://www.apache.org/dist/jakarta/jakarta-bsf/release/v2.3/src/";></a>
-->
- Download the source release</li>
+ <a
href="http://www.apache.org/dist/jakarta/jakarta-bsf/release/v2.4/src/";>
+ Download the source release
+ </a>
+ </li>
+
+
+<!--
<li>
-<!--
<a
href="http://www.apache.org/dist/jakarta/jakarta-bsf/release/v2.3/rpms/";></a>
+ Download source or binary RPMs</li>
-->
- Download source or binary RPMs</li>
+
</ul>
</section>
@@ -145,12 +155,15 @@
<a href="http://www.apache.org/dist/jakarta/jakarta-bsf/dev/v2.4.0/src/";>
Download the development source release</a>
</li>
+
+
+<!--
<li>
-<!--
<a href="http://www.apache.org/dist/jakarta/jakarta-bsf/dev/v2.3.0/rpms/";></a>
--->
Download development source or binary RPMs
</li>
+-->
+
</ul>
</section>
Index: xdocs/bsfnews.xml
===================================================================
--- xdocs/bsfnews.xml (revision 449215)
+++ xdocs/bsfnews.xml (working copy)
@@ -9,11 +9,10 @@
</properties>
<body>
- <section name="BSF 2.4">
- <h3>September, 16, 2006 - BSF 2.4.0 RC 2 Available</h3>
+ <section name="BSF 2.4.0">
+ <h3>September, 25, 2006 - BSF 2.4.0 Available</h3>
<p>
- The second development release candidate 2 version of BSF 2.4 from Apache
Jakarta is
- now available for
+ The release of BSF 2.4 from Apache Jakarta is now available for
<a href="http://jakarta.apache.org/builds/jakarta-bsf/dev/v2.4.0/";>
download</a>. If you have any feedback on this release, feel free to
join the discussion on the bsf-dev and bsf-user mailing lists.
Index: xdocs/projects.xml
===================================================================
--- xdocs/projects.xml (revision 449215)
+++ xdocs/projects.xml (working copy)
@@ -394,10 +394,22 @@
Recommendations for XSL Transformations (XSLT) and the XML Path
Language (XPath). It can be used from the command line, in an applet
or a servlet, or as a module in other program.
+ </p>
- <br></br>
- Starting with Sun's Java 1.4SE a W3C compliant set of classes for XSLT
is part
- of the runtime environment."
+ <p><em>Hint:</em>
+ Starting with Sun's Java 1.4SE a W3C compliant set of classes for
XSLT is part
+ of the runtime environment.", <em>however</em>, with other
versions of
+ Java or newer versions of Xalan distributions you <em>may</em>
need to explicitly extract the
+ archive
+ <em><code>xalan.jar</code></em> and put it into the
<code>CLASSPATH</code>
+ environment variable or alternatively, copy it into the Java
<em><code>endorsed</code></em> or
+ <em><code>ext</code></em>ension directory of your
+ Java distribution (usually in
<code>$(JAVA_JRE_HOME)/jre/lib/{endorsed|ext}</code>). The download
+ site of Xalan (Java version) is at: <a
href="http://xml.apache.org/xalan-j/downloads.html";>http://xml.apache.org/xalan-j/downloads.html</a>
+ <br></br>
+ (You can determine quite easily whether you need to do that: just
try to run the <code>xslt</code> sample
+ of the BSF distribution. If you encounter the error <code> 'Could
not compile stylesheet'</code>, then
+ you need to explicitly supply the <code>xalan.jar</code> from the
Xalan distribution.)
</p>
<table>
Index: TODO.txt
===================================================================
--- TODO.txt (revision 449215)
+++ TODO.txt (working copy)
@@ -1,3 +1,26 @@
+For 2006-09-25 the TODO list would consist at least from the following items:
+
+ - add new BSF engines for BSF 2.4
+
+ - create a new BSF 3.0 which complies to JSR-223 (which is part of
Java 1.6),
+ some features being
+
+ - BSF 3.0 will be available as FOSS for earlier version of Java
+
+ - BSF 3.0 may get an internal adapter for employing the numerous BSF
2.4
+ engines transparently
+
+ - ...
+
+
+Rony G. Flatscher, 2006-09-25
+
+
+
+------------------------------ cut here (from 2003)
-----------------------------
+The following TODO list stems from 2003 and has not been updated anymore and
+has partially been obsoleted:
+
TODO list for BSF 2.3.0-1:
use a discovery mechanism like JAXP in place of Languages.properties
@@ -22,3 +45,7 @@
TODO list for BSF 3.0.0:
address debug support for multiple languages (JSR-045?)
+------------------------------ cut here (from 2003)
-----------------------------
+
+
+
Index: CHANGES.txt
===================================================================
--- CHANGES.txt (revision 449215)
+++ CHANGES.txt (working copy)
@@ -15,10 +15,11 @@
the newer 'org.apache.bsf.engines.jython'
*) 'org.apache.bsf.BSFMain.java': new method
- "public String getVersion()", returns string in the form
- 'abb.yyyymmdd', where 'a' is major number, 'bb' minor number,
- 'yyyy' four digit year, 'mm' two digit month, 'dd' two digit day;
- e.g. '240.20060909' stands for: BSF version 2.4 as of 2006-09-09
+ "public String getVersion()", returns string in the form of a
+ dewey decimal number 'abc' (three levels, each between 0 and 9)
+ 'abc.yyyymmdd', 'yyyy' four digit year, 'mm' two digit month,
+ 'dd' two digit day;
+ e.g. '240.20060925' stands for: BSF version 2.4.0 as of 2006-09-25
*) new class 'org.apache.bsf.utils.BSFEventProcessorReturningEventInfos'
Index: src/org/apache/bsf/BSFManager.java
===================================================================
--- src/org/apache/bsf/BSFManager.java (revision 449215)
+++ src/org/apache/bsf/BSFManager.java (working copy)
@@ -59,7 +59,7 @@
// version string in the form of: "abb.yyyymmdd",
// where "a" is the major version number, "bb" the minor version number,
// and "yyyymmdd" represents the date in sorted order (four digit year,
two digit month, two digit day)
- protected static String version="240.20060917";
+ protected static String version="240.20060925";
// table of registered scripting engines
protected static Hashtable registeredEngines = new Hashtable();
@@ -157,12 +157,15 @@
/** Returns the version string of BSF.
*
- * @return version string in the form ""abb.yyyymmdd"" where
- * "a" represents the major version number,
- * "bb" the minor version number,
- * "yyyy" four digit year,
- * "mm" two digit month, and
- * "dd" two digit day.
+ * @return version string in the form "abc.yyyymmdd" where
+ "abc" represents a dewey decimal number (three levels, each
between 0 and 9), and
+ "yyyy" a four digit year, "mm" a two digit month,
+ "dd" a two digit day.
+ *
+ <br>Example: "<code>240.20060925</code>"
+ stands for: BSF version <code>2.4.0</code> as of
<code>2006-09-25</code>.
+ *
+ *
* @since 2006-01-17
*/
public static String getVersion() {
Index: docs/problems.html
===================================================================
--- docs/problems.html (revision 449215)
+++ docs/problems.html (working copy)
@@ -165,7 +165,7 @@
else may have already encountered this problem, and perhaps it has
been fixed. The next step, therefore, may be to try a nightly build
of BSF to see if the problem has been fixed. Nightly builds for BSF
- are available from the
+ are available from the
<a href="http://www.apache.org/dist/jakarta/jakarta-bsf/nightly/";>
Jakarta web site</a>. While BSF nightly builds are typically quite
stable and are used by
@@ -232,9 +232,9 @@
correct values for the various inputs when creating the bug, such
as which version of BSF you are running, and on which platform,
etc. Once the bug is created, you can also add attachments to
- the bug report.
+ the bug report.
</p>
- <p>
+ <p>
What information should you include in your bug report? The
easiest bugs to fix are those that are most easily reproducible,
so it is really helpful if you can produce a small test case that
@@ -273,7 +273,7 @@
These are just a different type of bug report. If you look in the
bug database, you will see that one of the severity settings for
a bug is "Enhancement". Just fill the bug report in,
- set the severity of the bug to "Enhancement", and
+ set the severity of the bug to "Enhancement", and
state in the description how you would like to have BSF enhanced.
Again, you should first check whether there are any existing
enhancment requests that cover your needs. If so, just add your
@@ -295,7 +295,7 @@
try to find the cause of the problem and provide a fix yourself.
The best way to do that is by working with the latest code from
CVS.
Alternatively, you can work with the source code available from the
- <a
href="http://jakarta.apache.org/builds/jakarta-bsf/release/v2.3/src/";>
+ <a
href="http://jakarta.apache.org/builds/jakarta-bsf/release/v2.4/src/";>
source distributions</a>. If you
are going to tackle the problem at this level, you may want to
discuss some details first on the <nobr><code>bsf-dev</code></nobr>
@@ -322,8 +322,8 @@
<font face="verdana" size="-1">
cvs diff -u Javac.java > javac.diffs<br /><br />
</font>
-
- Note: You should give your patch files meaningful names.
+
+ Note: You should give your patch files meaningful names.
This makes it easier for developers who need to apply a number
of different patch files.
</p>
Index: docs/index.html
===================================================================
--- docs/index.html (revision 449215)
+++ docs/index.html (working copy)
@@ -225,17 +225,27 @@
<!--
<a href="http://www.apache.org/dist/jakarta/jakarta-bsf/release/v2.3/bin/";></a>
-->
- Download the binary release</li>
+ <a
href="http://www.apache.org/dist/jakarta/jakarta-bsf/release/v2.4/bin/";>
+ Download the binary release
+ </a>
+ </li>
+
<li>
<!--
<a href="http://www.apache.org/dist/jakarta/jakarta-bsf/release/v2.3/src/";></a>
-->
- Download the source release</li>
+ <a
href="http://www.apache.org/dist/jakarta/jakarta-bsf/release/v2.4/src/";>
+ Download the source release
+ </a>
+ </li>
+
+
+<!--
<li>
-<!--
<a
href="http://www.apache.org/dist/jakarta/jakarta-bsf/release/v2.3/rpms/";></a>
+ Download source or binary RPMs</li>
-->
- Download source or binary RPMs</li>
+
</ul>
</blockquote>
</td></tr>
@@ -260,12 +270,15 @@
<a href="http://www.apache.org/dist/jakarta/jakarta-bsf/dev/v2.4.0/src/";>
Download the development source release</a>
</li>
+
+
+<!--
<li>
-<!--
<a href="http://www.apache.org/dist/jakarta/jakarta-bsf/dev/v2.3.0/rpms/";></a>
--->
Download development source or binary RPMs
</li>
+-->
+
</ul>
</blockquote>
</td></tr>
Index: docs/bsfnews.html
===================================================================
--- docs/bsfnews.html (revision 449215)
+++ docs/bsfnews.html (working copy)
@@ -96,15 +96,14 @@
<table border="0" cellspacing="0" cellpadding="2" width="100%">
<tr><td bgcolor="#525D76">
<font color="#ffffff" face="arial,helvetica,sanserif">
- <a name="BSF 2.4"><strong>BSF 2.4</strong></a>
+ <a name="BSF 2.4.0"><strong>BSF 2.4.0</strong></a>
</font>
</td></tr>
<tr><td>
<blockquote>
- <h3>September, 16, 2006 - BSF 2.4.0 RC 2 Available</h3>
+ <h3>September, 25, 2006 - BSF 2.4.0 Available</h3>
<p>
- The second development release candidate 2 version of BSF 2.4 from Apache
Jakarta is
- now available for
+ The release of BSF 2.4 from Apache Jakarta is now available for
<a href="http://jakarta.apache.org/builds/jakarta-bsf/dev/v2.4.0/";>
download</a>. If you have any feedback on this release, feel free to
join the discussion on the bsf-dev and bsf-user mailing lists.
Index: docs/projects.html
===================================================================
--- docs/projects.html (revision 449215)
+++ docs/projects.html (working copy)
@@ -1063,11 +1063,22 @@
Recommendations for XSL Transformations (XSLT) and the XML Path
Language (XPath). It can be used from the command line, in an applet
or a servlet, or as a module in other program.
-
- <br />
- Starting with Sun's Java 1.4SE a W3C compliant set of classes for XSLT
is part
- of the runtime environment."
</p>
+ <p><em>Hint:</em>
+ Starting with Sun's Java 1.4SE a W3C compliant set of classes for
XSLT is part
+ of the runtime environment.", <em>however</em>, with other
versions of
+ Java or newer versions of Xalan distributions you <em>may</em>
need to explicitly extract the
+ archive
+ <em><code>xalan.jar</code></em> and put it into the
<code>CLASSPATH</code>
+ environment variable or alternatively, copy it into the Java
<em><code>endorsed</code></em> or
+ <em><code>ext</code></em>ension directory of your
+ Java distribution (usually in
<code>$(JAVA_JRE_HOME)/jre/lib/{endorsed|ext}</code>). The download
+ site of Xalan (Java version) is at: <a
href="http://xml.apache.org/xalan-j/downloads.html";>http://xml.apache.org/xalan-j/downloads.html</a>
+ <br />
+ (You can determine quite easily whether you need to do that: just
try to run the <code>xslt</code> sample
+ of the BSF distribution. If you encounter the error <code> 'Could
not compile stylesheet'</code>, then
+ you need to explicitly supply the <code>xalan.jar</code> from the
Xalan distribution.)
+ </p>
<table>
<tr>
<td bgcolor="#039acc" colspan="" rowspan=""
Index: build-properties.xml
===================================================================
--- build-properties.xml (revision 449215)
+++ build-properties.xml (working copy)
@@ -2,7 +2,7 @@
<project name="props">
<property name="project.name" value="bsf"/>
<property name="project.fullName" value="Bean Scripting Framework"/>
- <property name="project.version" value="2.4.0-RC2-20060916"/>
+ <property name="project.version" value="2.4.0-20060925"/>
<property name="project.debug" value="on"/>
<property name="project.deprecation" value="on"/>
Index: build.xml
===================================================================
--- build.xml (revision 449215)
+++ build.xml (working copy)
@@ -67,7 +67,7 @@
Olivier Gruber <[EMAIL PROTECTED]>
Copyright:
- Copyright (c) Apache Software Foundation 2004. All Rights Reserved
+ Copyright (c) Apache Software Foundation 2004-2006. All Rights Reserved
==================================================================== -->
Index: RELEASE-NOTE.txt
===================================================================
--- RELEASE-NOTE.txt (revision 449215)
+++ RELEASE-NOTE.txt (working copy)
@@ -18,7 +18,7 @@
=========================
-BSF 2.4, RC 1, 2006-09-09
+BSF 2.4, 2006-09-25
=========================
=========================================================
@@ -73,10 +73,11 @@
the newer 'org.apache.bsf.engines.jython'
- 'org.apache.bsf.BSFMain.java': new method
- "public String getVersion()", returns string in the form
- 'abb.yyyymmdd', where 'a' is major number, 'bb' minor number,
- 'yyyy' four digit year, 'mm' two digit month, 'dd' two digit day;
- e.g. '240.20060909' stands for: BSF version 2.4 as of 2006-09-09
+ "public String getVersion()", returns string in the form of a
+ dewey decimal number 'abc' (three levels, each between 0 and 9)
+ 'abc.yyyymmdd', 'yyyy' four digit year, 'mm' two digit month,
+ 'dd' two digit day;
+ e.g. '240.20060925' stands for: BSF version 2.4.0 as of 2006-09-25
- new class 'org.apache.bsf.utils.BSFEventProcessorReturningEventInfos'
Index: BUILDING.txt
===================================================================
--- BUILDING.txt (revision 449215)
+++ BUILDING.txt (working copy)
@@ -1,35 +1,39 @@
-To build BSF, one needs the following:
+From the ant "build.xml" file:
- Servlet API .jar via Tomcat or other source
- Supported language .jar files:
+ Master Build file for BSF
+Notes:
+
+ This is the build file for use with the Jakarta Ant build tool.
+
+Optional additions:
+
BeanShell -> http://www.beanshell.org/ (3rd party BSF engine)
+ JRuby -> http://www.jruby.org/ (3rd party BSF engine)
Jacl -> http://www.scriptics.com/java/
- JPython -> http://www.jpython.org/
- JRuby -> http://www.jruby.org/ (3rd party BSF engine)
+ JavaScript -> http://www.mozilla.org/rhino/
JudoScript -> http://www.judoscript.com/ (3rd party BSF engine)
Jython -> http://www.jython.org/
NetRexx -> http://www2.hursley.ibm.com/netrexx/
- Rhino -> http://www.mozilla.org/rhino/
- Xalan -> http://xml.apache.org/xalan/
+ Xalan -> http://xml.apache.org/xalan-j
-As a convenience, these language .jars are currently collected at:
+Build Instructions:
- http://www.topsail.org/goodies/BSFlang/
+ To build, run
-Make sure the .jars (and Ant) are in your CLASSPATH, and then use the command
+ java org.apache.tools.ant.Main <target>
- ant [target]
+ on the directory where this file is located with the target you want.
-where [target] is one of the following:
+Most useful targets:
- compile creates the "bsf.jar" package in "./build/lib"
- (default target)
- samples compiles the samples into "./build/samples"
- javadocs creates javadocs for the whole package in
- "./build/javadocs"
- bindist creates the complete binary distribution in "./dist/"
- srcdist creates the complete src distribution in "./dist/"
- dist creates both the binary and the src distributions
- in "./dist/"
- clean removes all the generated files and directories
+ - all -> creates the binary and src distributions, and builds the site
+ - bindist -> creates the complete binary distribution in "./dist/"
+ - build-site -> creates the website in "./docs"
+ - clean -> removes all the generated files and directories
+ - compile -> creates the "bsf.jar" package in "./build/lib" (default
target)
+ - dist -> creates both the binary and the src distributions in "./dist/"
+ - javadocs -> creates the javadocs in "./build/javadocs"
+ - samples -> creates/compiles the samples into "./build/samples"
+ - srcdist -> creates the complete src distribution in "./dist/"
+
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
