2 * separate security into product and test where test depends on JPA 2.0 implementations
3 and test is not deployed to the central maven repo.
4 * move codestyle to separate svn project.
6 * refactor: Create jpa subproject with separate subprojects for api, hibernate,
7 toplink-essentials and eclipselink
8 Each subproject contains the required repo settings
10 * update mythtv project for java ee 6
11 * add schemagen for user management part.
12 * reimplement photos application using wicket
13 * JPA 2.0 implementation for security.
15 * change tracking for all projects with changes plugin
17 * complete presentation of all wamblee stuff on wamblee.org.
18 * maven sites for each subproject accessible through wamblee.org
19 * overview pages for separate areas
21 * create passwords application