THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- Use Git instead Svn
- Switch to Java 67
- 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 PluginsPlugins
- 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
- 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
- Themes cleanup
- Support HTML 5 features and Single Page Application development paradigm
- Must output valid markup
- Should be compatible with bootstrap, bootstrap validator, and other major UI platforms
...
- Request Git repo from INFRA
- Import project
- Remove deprecated plugins - moved to struts-archive.git repo
- we need place for deprecated stuff (to move the source code to) - new project "struts-archive"
- drop support for Struts 1 (remove plugin)
- dojo plugin
- codebehind plugin
- jsf plugin
- if it cannot be removed, mark to be removed during work on 3.0
Remove deprecated APIs- Switch to Java 7
- Merge XWork code into Struts Core (without renaming packages)
- Switch to strict DMI by default - allow only defined methods to be accessible via DMI - user can always change that listPrepare the first beta release
- Mark current logging layer as
@deprecated
and use Log4j2 as default one - Implement plugin
- Add showcase example
- Add documentation to wiki
Add plugin to support bean validation- Upgrade spring plugins spring version to 4.x
- Prepare the first releaseMove struts2 blank, jboss-blank and mailreader app to struts2-examples
- Switch to strict DMI by default - allow only defined methods to be accessible via DMI - user can always change that list
- prepare second beta
- drop support for "top" object - this can be painful, users are using so migration path is needed
- new user guide totally developed out of Confluence - people will be able to contribute to it via GitHub
- Confluence (wiki) used only to explain more detailed given aspect of the framework (ie.: how to implement your own converter in details)
- keep just one version of the doc (no more release/2.3.x, release/2.2.x and so on - Google indexes everything and people are confused)
Cleanup website- prepare the last beta
...
M2 (
...
aka Struts 2.6)
Servlets 2.5, JSP 2.1, Java 7
struts-api
module- Drop support for internal logging layer and use Log4j2 only
M3 (beta 1 Struts 3)
- Servlets 3.0, JSP 2.2, Java 8
- Finish merging XWork code base (rename packages)
- Rename Struts 2 packages to org.apache.struts3Use logging layer from Log4j2 or https://code.google.com/p/anodyzed/ (Chris Pratt is willing to donate that project to Struts)
- Switch to OGNL 4
- we must release it first
- also we need better API interfaces to allow integrate Struts with other EL engines, ie.: MVEL - right now the whole conversion layer is hardly tied with OGNL
- Switch to Servlet Specification 3.0
- drop embedded JSP plugin
...
- Divide core into api and spi
M4 (beta
...
2 Struts 3)
- move plugins to separated project (need to be discussed)
- disconnect plugins release cycle from core release
...