In order to have a solid 1.0 release of Spring Rich, the following is absolutely required:

• Documentation
  • complete javadoc
  • tutorial
  • sample applications covering the major features

• Testing
  • a full test suite
• Build
  • use the Spring common build system
  • "Juergen-ized"
    • Like the core Spring project, the subsystems need to be fully decoupled, with consistent naming and ways of doing things
• View support
  • extract functionality from ApplicationDialog into a new generic view class which can be used in (internal) frames

These things would be very nice, but not absolutely required:

• tight Acegi integration