Thanks Stefan!
For Sling 14 and Jakarta Servlet, we should quickly decide whether the
current approach is the way we want to go. If the answer is yes, I
covered already some grounds in branches and think that some modules are
more or less ready to go (minus potential bugs I might have introduced).
PAX Exam tests which require a complete Sling including a JCR repository
are currently a problem, and the whole scripting machinery needs some
updates for Jakarta. I don't think this is a ton of work. It needs
careful handling of the two cases (javax servlet and jakarta servlet)
and a lot of eyes on the PRs.
Regards
Carsten
On 17.01.2025 11:49, Stefan Seifert wrote:
sling 13 release is done. it took a bit longer than expected due to several
tooling issues around further switching to Java 17 and to Java 21 since the
last release, and I took a bit more time to fix the root causes around the
tooling problems, and tried to simplify the process at some places. however,
the whole process was already very well prepared by robert over the last years,
thanks for this good foundation, robert!
looking forward for Sling 14, it would be nice to include:
- Supporting Jakarta Servlet Specification
- Getting rid of javax.json completely and finalizing the switch to jakarta.json
- Rename the remaining related modules/github repos from "launchpad" to starter
to get rid of the old name
as discussed in the last meetings, we should not wait again 2,5 years with the
next release. this is not only looking strange from outside, it also comes with
the risk of accumulating lots of potential problems which then makes doing a
new release harder. normally, doing a sling starter release should not take
that much of time with a lot of road blocks removed. so maybe 2 releases in a
year would be fine from my point of view.
stefan
--
Carsten Ziegeler
Adobe
[email protected]
