-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Future of Spark #1102
Comments
You're my hero! Will you be building on top of Javalin? |
@RyanSusana That is one possible way, I have yet to investigate that option on a deep level. However, there are several parameters to weigh in when taking that decision. The working plan has been continuing on the Spark baseline with the solution to build upon javelin as a possibility if deemed beneficial. The plan is either way to fixing som crucial issues and make a 2.9.0 release soon and thereafter start work on the 3.0 release. I am currently compiling a list of must-haves and nice-to-haves in Spark 3.0 and I'll be posting continuously here in this tread and on the Spark twitter page everytime there an update. |
Looking forward to it, I have written some interfaces to Sparkjava/Javalin in my CMS framework. Did this, so I can switch between both and then eventually any functional style micro-framework. I would be happy to contribute. |
I would love to see a 2.9 release soon. Happy to help on PRs if we can make a roadmap or list of features we need to see. |
@robax the plan is to make a 2.9.0 release next week. It'd very much appreciate any help. Is there any particual issues/PRs you'd like to see in 2.9.0? |
I had a couple.
|
It would be awesome if #1049 could make it into 2.9.0. |
I just want to see #1049. If you want to release next week (which would be awesome), then probably just going through and merging open PRs is the best plan of attack? Then we can work on new features for the 3.0 release. |
Thanks for the quick release! @perwendel |
Please support render raw jsp. for example: get("/url", (q, a) -> jsp("/x.jsp"); // or support servletDispatch to WEB-INF/jsp file. this would help to upgrade the legacy code. Thanks!! |
You should really think about renaming the framework as the name collides with Apache Spark. Querying for solutions land up with Apache Spark results on Google. |
As you probably have noticed the project has been in hibernation for a couple of months. The reason to this are mainly personal reasons.
However, the plan is to ramping up development of Spark. The plan is to make a 3.0 release where the API is revised and improved where possible and relevant extensions are made. The kotlin framework also needs an official release.
The text was updated successfully, but these errors were encountered: