[maven-release-plugin] prepare release wamblee-utils-0.2.3

[utils] / TODO.txt

diff --git a/TODO.txt b/TODO.txt
index 6efaa9132473f8ce798b3107ff8e41e3528aa716..ac2f1ab1bfe73ba5241c6d3ea73e7991b99de90b 100644 (file)
--- a/TODO.txt
+++ b/TODO.txt
@@ -1,12 +1,20 @@
  
-* refactor: Create jpa subproject with separate subprojects for api, hibernate, 
-  toplink-essentials and eclipselink
-  Each subproject contains the required repo settings
-* Maven profile for nonrelease which is dactivated when release is active.
-* Have toplink, eclipselink, hibernate profiles that are deactivated by 
-  release and active by default. 
-  
-* add cdi subproject to the utils
-* add schemagen for user management part. 
-* JPA 2.0 implementation for security. 
+* DatabaseUtils: deletion of tables must be more generic
+  First drop all constraints then drop all tables. 
+  Or use JPA to drop the tables but that is a short-term solution 
+* Get rid of use of detached objects in security
+  - Use only basic types in UserAdministration
+  - Put API in separate package 
+* add cdi subproject
+ 
+* update mythtv project for java ee 6 
+* reimplement photos application using wicket
+
+* change tracking for all projects with changes plugin
 
+* complete presentation of all wamblee stuff on wamblee.org. 
+* maven sites for each subproject accessible through wamblee.org
+* overview pages for separate areas
+
+* create user mgt application
+