commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From commons-...@jakarta.apache.org
Subject [Jakarta Commons Wiki] Updated: JEXL
Date Thu, 19 Aug 2004 17:40:27 GMT
   Date: 2004-08-19T10:40:27
   Editor: DionGillard <dion@apache.org>
   Wiki: Jakarta Commons Wiki
   Page: JEXL
   URL: http://wiki.apache.org/jakarta-commons/JEXL

   no comment

Change Log:

------------------------------------------------------------------------------
@@ -10,8 +10,8 @@
 
 JEXL has been sitting around for some time (some might say, it has been languishing).  A
few projects (such as Jelly) use it, but more would use it if it were fully releases.  Plus,
components in commons proper should be released.  So, let's make a release of JEXL sooner
rather than later, here's the process:
 
- * '''Code review for any outstanding issues''' - We need to give JEXL a once over to make
sure there are no obvious outstanding issues or bugs that need fixing.
- * '''Call for Comments''' - Once we are certain there are no outstanding issues, call for
comments on commons-dev
+ * '''Code review for any outstanding issues''' - We need to give JEXL a once over to make
sure there are no obvious outstanding issues or bugs that need fixing. (DONE)
+ * '''Call for Comments''' - Once we are certain there are no outstanding issues, call for
comments on commons-dev. (DONE)
  * '''Cut a release'''
  * '''Publish to Maven repo'''
 
@@ -19,11 +19,14 @@
 
  * '''Documentation'''
    * '''Syntax Page''' - We need a page devoted to syntax, preferably we'll have an explanation
of the syntax and a big table with some examples.
+      * Placeholder created
    * '''Examples Page''' - Keep the small example on the front page, we'll need a quick page
that reads like a small user's guide with a section demonstrating every usage situation.
+      * Placeholder created
    * '''Related Resources on Index Page''' - Develop this related resources section put some
more links to Velocity resources.
    * '''package.html''' - Some of the packages have package.html content.  We need to make
sure that a developer has the necessary tools to use Jexl from the Javadoc alone.
    * '''JavaDoc''' - We need some explanation about Pre and Post resolvers.  Esp. why and
how someone would ever want to use them.  Also, keep an eye out for informal JavaDoc - the
jexl package had some JavaDoc that sounded like development planning.
 
  * '''Refactoring'''
    * '''Unused Classes''' - There was one class (sort sort of LogAdapter) which was not referenced
in thie commons-jexl project.  Make sure that each class in jexl is relevant.
+      * Other than unused parser classes, all now appear to be used.
    * '''General Refactoring''' - How's that for a catch all bullet point?

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message