Struts Next

What should be improved / changed

Issues connected with the new version
Build of the latest version

• 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 1.6
• Update "internal" injection to use current Guice.
• 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.
• Adopt slf4j as new logging framework: this allows developers to plug-in any logging framework they want.
• Consider renaming packages to org.apache.struts3
• Remove deprecated Plugins
  • Codebehind
  • Dojo
• 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

Plan for Struts 2.5

1. Request Git repo from INFRA
2. Import project
3. Remove deprecated plugins
4. Drop support for Struts 1 (remove plugin)
5. Remove deprecated APIs
6. Switch to Java 1.6
7. Prepare the first release
8. Rename XWork packages to org.apache.struts.xwork

Plan for Struts 3

1. Rename Struts 2 packages to org.apache.struts
2. ...