pippo-java
Pippo 2 roadmap
I think that is time to talk about Pippo 2.x roadmap. Pippo is maintained under the Semantic Versioning guidelines, so in a new major version (2.0 in our case) we can make incompatible changes in our API. Now is time to improve Pippo without to care about backward compatible.
I will try to add some proposes:
- Servlet 4 and HTTP2 (#490)
-
ErrorHandlerwould handleThrowable(#503) - Migrate to JUnit 5 (#505)
The list with proposes will grow in time.
If you think that something is bad designed or you want to change something in the current API, please add a comment.
I created Pippo 2 milestone and added some issues (maybe not all). In this mode we can make more transparent, which issues need to be resolved (or are already resolved) for the next major release.
If you plan to support Java 11+ (LTS) for Pippo 2, then I may have a proposal:
- Pippo should be a module --> Java Platform Module System (JPMS)
Actually I see some direct and indirect conflicts causing by pippo and third-party dependencies with JPMS. Minimum would, however, be a fixed module name and make your module open with open module ... {}. Actually maven complains about:
[INFO] Required filename-based automodules detected: [pippo-core-1.12.0.jar, pippo-gson-1.12.0.jar, gson-2.3.1.jar, pippo-controller-1.12.0.jar, pippo-guice-1.12.0.jar]. Please don't publish this project to a public artifact repository!
See what I proposed to do (for another project): https://github.com/vy/rotating-fos/issues/11
We can try to improve the receipt of http request parameters. Like conversion and validation (Bean Validation maybe).
Related issues:
- https://github.com/pippo-java/pippo/pull/208
- https://github.com/pippo-java/pippo/issues/489
- https://github.com/pippo-java/pippo/issues/524
Conducting a survey of open issues for Pippo 2 is also a good thing.
Finally, we started working on this topic.
I created branch 1.x in case we need to fix some major/critical bugs for people that cannot switch to Java 11 from different reasons.