You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by rl...@apache.org on 2003/12/15 07:34:35 UTC
cvs commit: jakarta-commons/validator/xdocs navigation.xml tasks.xml
rleland 2003/12/14 22:34:35
Modified: validator/xdocs navigation.xml tasks.xml
Log:
Doc a few items
Revision Changes Path
1.3 +1 -0 jakarta-commons/validator/xdocs/navigation.xml
Index: navigation.xml
===================================================================
RCS file: /home/cvs/jakarta-commons/validator/xdocs/navigation.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- navigation.xml 22 Aug 2003 04:15:48 -0000 1.2
+++ navigation.xml 15 Dec 2003 06:34:35 -0000 1.3
@@ -10,6 +10,7 @@
<item name="Community" href="/community.html"/>
<item name="To Do List" href="/tasks.html"/>
<item name="Resources" href="/resources.html"/>
+ <item name="Javascript Javadoc" href="/javascript/org/apache/commons/validator/javascript/allclasses-summary.html"/>
<item name="Legacy 1.0.2" href="/1.0.2/api/org/apache/commons/validator/package-summary.html"/>
</menu>
</body>
1.7 +9 -2 jakarta-commons/validator/xdocs/tasks.xml
Index: tasks.xml
===================================================================
RCS file: /home/cvs/jakarta-commons/validator/xdocs/tasks.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- tasks.xml 15 Dec 2003 06:10:51 -0000 1.6
+++ tasks.xml 15 Dec 2003 06:34:35 -0000 1.7
@@ -24,6 +24,12 @@
<subsection name="Medium priority">
<ul>
+ <li>
+ Integrate the creation of javascript javadocs into the maven build. What will need to happen
+ is something similar to the exec task in the ant build.xml. Then to put a Maven template around
+ the javadoc it and the legacy 1.0.2 javadoc will need to be copied to a temporary directory then the
+ html2xdoc task will need to be run against that temporary directory.
+ </li>
<li>
Change the validation.xml file semantics to match a more general "bean" validation usage.
Currently, the <form-validation>, <formset>, <form>, and <field> elements
@@ -32,7 +38,7 @@
non-form based environments.
</li>
<li>
- Scenario one:
+ Scenario one:
Replace the Jakarta ORO regex engine with the standard Java 1.4 engine. Preliminary tests show a
50% speed improvement using the standard engine. This will remove the ORO dependency and
bring Validator in line with standard Java regular expressions. However, this requires a move
@@ -40,7 +46,7 @@
we also change the configuration file semantics.
</li>
<li>
- Much more likely Scenario:
+ More likely Scenario:
ORO provides a much richer interface to regular expression, such that we don't have
to worry about bit twiddling, this includes a pluggable regex engine. Jeffrey E Friedl states
in Mastering Regular Expressions 2ed, says that in speaking to the ORO developers that they
@@ -84,6 +90,7 @@
<li>
Add ability to use required condition on array types like checkboxes.
</li>
+ </ul>
</subsection>
<subsection name='Since 1.0.2 Release'>
<ul>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org