Page History

...

• 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 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

Plan for Struts 2.5

•  Request Git repo from INFRA

...

•  Import project

1. Remove deprecated plugins
2. Drop support for Struts 1 (remove plugin)
3. Remove deprecated APIs
4. Switch to Java 1.6Rename XWork packages to org.apache.struts.xwork
5. Merge XWork code into Struts Core (without renaming packages)
6. Prepare the first release
7. Cleanup website

Plan for Struts 3

1. Finish merging XWork code base (rename packages)
2. Rename Struts 2 packages to org.apache.struts...struts3
3. Use loggin layer https://code.google.com/p/anodyzed/
4. Divide core into api and spi
5. prepare ALPHA release

Cleanup website

There should be just one project website - Apache Struts. Right now there is the main website - Apache Struts project, subsite Apache Struts 1 and another subsite Apache Struts 2. After announcing EOL of Struts 1, we basically supporting just one version or rather branch - Apache Struts 2 which should be at some point converted just into Apache Struts (version 2.5, version 3.0, version 3.1, etc.).

...