Author: nbubna
Date: Thu Oct 20 10:19:29 2005
New Revision: 326950
URL: http://svn.apache.org/viewcvs?rev=326950&view=rev
Log:
update status and readme
Modified:
jakarta/velocity/tools/trunk/README.txt
jakarta/velocity/tools/trunk/STATUS
Modified: jakarta/velocity/tools/trunk/README.txt
URL:
http://svn.apache.org/viewcvs/jakarta/velocity/tools/trunk/README.txt?rev=326950&r1=326949&r2=326950&view=diff
==============================================================================
--- jakarta/velocity/tools/trunk/README.txt (original)
+++ jakarta/velocity/tools/trunk/README.txt Thu Oct 20 10:19:29 2005
@@ -66,16 +66,16 @@
> ant example.struts
+To build the VelocityLayoutServlet example, execute:
+
+> ant example.layout
+
Please note:
-- To compile VelocityStruts with JDK 1.3, you *must* define a jdbc.jar property
- somewhere in your build.properties or the build.properties provided with this
- project.
-
-- When building the javadoc with JDK 1.3, you will get a number of warnings if
you
- do not have a xerces.jar property defined somewhere in the build.properties.
- However, these warnings can generally be ignored.
+- Due to new compile-time dependencies, VelocityTools can only be compiled on
JDK 1.4
+ or higher. But can still be run on JDK 1.3, provided you are willing to do
without
+ some newer features, like the BrowserSnifferTool.
- During the documentation build process DVSL emits several of the following
error
messages. They can be ingnored. A bug report has already been filed.
@@ -86,9 +86,9 @@
involving java.net.URLEncoder. This is to maintain compatibility with JDK
1.3.
However, when running the code on 1.4, the new, non-deprecated method is
used.
-The build process has been tested with JDK 1.3.1 and JDK 1.4.1. The
-included example applications have been tested with Tomcat 4.0.4,
-Tomcat 4.1.24, and Resin 2.1.0.
+The build process has been tested with JDK 1.4.2 and JDK 1.5.0. The
+included example applications have been tested with Tomcat 5.0.30
+and Tomcat 5.5.9, but should work with any servlet engine.
If you observe any problems with the build process, please report this
to the Velocity users mailing list, velocity-user@jakarta.apache.org, and
@@ -111,4 +111,4 @@
We welcome your feedback to [EMAIL PROTECTED]
-$Revision: 1.10 $ $Date: 2003/07/10 21:18:22 $
+$Revision$ $Date$
Modified: jakarta/velocity/tools/trunk/STATUS
URL:
http://svn.apache.org/viewcvs/jakarta/velocity/tools/trunk/STATUS?rev=326950&r1=326949&r2=326950&view=diff
==============================================================================
--- jakarta/velocity/tools/trunk/STATUS (original)
+++ jakarta/velocity/tools/trunk/STATUS Thu Oct 20 10:19:29 2005
@@ -4,7 +4,7 @@
Known Issues/Bugs:
- - see bugzilla
+ - see http://issues.apache.org/jira/browse/VELTOOLS
@@ -23,6 +23,7 @@
VelocityView:
- add a library of velocimacros for use with these tools
+ - Add a standalone toolbox manager
- Pluggable toolbox manager in VelocityViewServlet
- Tool pooling support (use commons-pool probably)
- add chooseCharacterEncoding(req) to VVS to make dynamic encoding
@@ -41,12 +42,18 @@
(this would probably work in concert with the velocimacro libraries)
+Ideas being considered for version 2.0:
+ - Toolbox support for non-servlet environments
+ - Pluggable toolbox readers
+ - Support for reading toolbox from properties files
+ - Drop ViewTool and Configurable interfaces in favor of finding required
methods by reflection
+
Example Ideas:
- a blank Velocity-Struts application as the starting point for development.
- an application to demonstrate use of more obscure features like the
AbstractSearchTool, MultiViewsTool, IteratorTool, and the like.
- - Struts 1.1 example(s). Take the existing Struts 1.1 examples and replace
+ - Struts 1.3 example(s). Take the existing Struts 1.3 examples and replace
the view layer with Velocity. (show off Tiles, modules, Validator, etc.)
- example app(s) to demonstrate the velocimacro libraries
- self-documenting apps to explain and demonstrate key features
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
