...

• Use Git instead Svn 
  • Use Git flow to manage the repo and development process
    • http://nvie.com/posts/a-successful-git-branching-model/
    • https://github.com/nvie/gitflow
    • http://jeffkreeftmeijer.com/2010/why-arent-you-using-git-flow/
• Switch to Java 6
• Update "internal" injection to use current Guice version
  • Consider usage of http://onami.apache.org/
• Refactorings for further extensibility based on questions on the list, on CodeRanch, and Stack Overflow
  • JR plugin refactoring. Allow compiled reports as classpath resources.
• Refactor conversion of primitives (and wrappers) in XWork
• Switch to OGNL 4.0.
• Consider renaming packages to org.apache.struts3
• Remove deprecated Plugins
  • Codebehind
  • Dojo
  • Struts1 ?
• Normalize property name camel-casing (foo.bar.BazPlugh to foo.bar.bazPlugh)
• Check possible usage of Tiles Auto Tag (http://tiles.apache.org/tiles-autotag/) instead of Struts Annotations
• Convention plugin should be the "normal" way of using Struts
• Support HTML 5 features and Single Page Application development paradigm
• Plugin to map websocket requests to Struts actions
• API to customize property finding via arbitrary request parameter names ("a" -> getFoo())
  • Happily breaks apart the 1:1 relationship between property paths and HTTP parameter names
  • Will be useful for obfuscation (doesn't expose java model)
  • Can be used to shorten request payload (smaller names)
  • Can be taken advantage by HDIV

Development plan of Struts 3

...