Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Jakarta-commons Wiki" 
for change notification.

The following page has been changed by JörgSchaible:
http://wiki.apache.org/jakarta-commons/id/1%2e0ReleasePlan

The comment on the change is:
Update status.

------------------------------------------------------------------------------
   * Review UUID implementation and verify the spec compliance 
[[http://www.ietf.org/rfc/rfc4122.txt RFC 4122]]
    * Verify spec compliance
    * Check against JDK 1.5 functionality
-   * Introduce a UUIDIdentifierGenerator interface extending 
StringIdentifierGenerator with extended functionality to get the identifier 
directly as UUID or additionally as byte array.
+   * Introduce a UUIDIdentifierGenerator interface with extended functionality 
to get the identifier directly as UUID or additionally as byte array.
+   * Introcuce a UUIDStringIdentifierGenerator as wrapper for a 
UUIDIdentifierGenerator
    * Review the internal plugin mechanism (may drop dependency to 
commons-discovery and commons-logging)
    * Fix persistent store of State (ensure usability in system class path and 
application class path)
+   * Allow multiple instances of VersionOneGenerator to support IoC containers
-  * Drop IdentifierGeneratorFactory and IdentifierUtils
+  * Drop IdentifierGeneratorFactory and IdentifierUtils (./)
    This elements used static versions of each available IdentifierGenrator 
implementation and parametrization to provide a convenient way to access the 
generators available in commons-id. With the addition of new generator 
implementations the convenience for users vanish in combination with the 
maintainability.
   * Refactor PrefixXXXGeneratorIdentifier implementations
    It might be useful for all String-based generators to decorate the created 
identifier. The 3 current prefix implementations should be replaced by a 
generic decorator or transformator approach.
@@ -35, +37 @@

   * Clean-up exception handling
    Some methods have currently signatures for exceptions they do not throw. 
Some code throws a simple RuntimeException instead of introducing a derived 
exception for the commons-id components. A lot of internally runtime exceptions 
are not mentioned in the javadoc.
   * Improve test path coverage and fix remaining style issues
-  * Unify initialization of unit tests
+  * Unify initialization of unit tests (./)
-   A lot of unit tests use a suite method, have a constructor to parametrise 
the name and have a main method. All of this is normally not necessary in 
modern IDEs. In Eclipse this is even worse, since you cannot click on the run 
tests to switch to the test's source. '''Done.'''
+   A lot of unit tests use a suite method, have a constructor to parametrise 
the name and have a main method. All of this is normally not necessary in 
modern IDEs. In Eclipse this is even worse, since you cannot click on the run 
tests to switch to the test's source.
   * Check year of copyright in touched files
    
  === Documentation ===

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to