The main goal of Scalatra 2.6.x is to decrease future maintenance efforts and costs, since there are not enough active committers to maintain the existing huge codebase. To achieve this goal, I propose the followings:
- Follow the Scala standards (e.g. Twirl instead of Scalate, ScalaTest instead of Specs2)
- Deprecate modules that are not used much or not maintained enough
More specific tasks:
- Upgrade libraries and Jetty
- Remove all deprecated classes and methods
- Adopt Twirl as the default template engine (Update g8 template)
We have many modules in Scalatra, too many to be maintained by the current active committers. I wish to drop unimportant or outdated modules in the future, so I propose to deprecate or merge some modules as follows:
- Deprecate Swagger 1.x support
- Deprecate scalatra-swagger-ext or merge it to scalatra-swagger
- Deprecate scalatra-commands and introduce scalatra-forms instead
- Deprecate scalatra-spring
- Deprecate scalatra-specs2
- Drop scalatra-example because we have examples in scalatra-website-example
- Merge scalatra-fileupload to scalatra-core
- Any other candidates?
All deperecated features in 2.6 will be dropped in 2.7 or 3.0