Hi, The virtual round table took place this Monday and we had the opportunity to discuss some of the topics that were proposed. Some good ideas were put forward so I'm relaying them back to the dev list for further discussion.
They are written down at [1] and also pasted below. To continue the conversation, please reply to this email and change the subject, making sure to only quote the relevant part of the meeting notes. Thanks! Robert [1]: https://cwiki.apache.org/confluence/display/SLING/Virtual+Round+Table+-+November+2021#VirtualRoundTableNovember2021-Meetingnotes --- 1. How to prevent default servlets (mainly POST default servlet) from kicking in? Multiple variants were discussed, with the consensus arriving at implementing a new POST operation that handles this. 3. Status of Sling 12 - Mostly blocked by finalising the feature model migration work. Most important topic - what is the recommended way to launch the Sling Starter? - simple docker run - download feature launcher and execute with a remote feature file - kickstart jar (not yet implemented) - clone starter from GitHub and launch - perhaps with a default launcher based on the maven- exec-plugin - should we present multiple options to users, e.g. docker run for one-off and archetype generation for starting projects? 6. HTL Whitespace removal The discussion converged around a new HTL command that will provide this. Other scripting engines, like Thymeleaf, presumably have this capability so we don't need to implement something for every engine. 7. Support for Java 8 - no concrete proposal on when it should happen - it's important to increment the minor version of a bundle when changing requirements. - Java version change - Supported OSGi specs version, e.g. R6 → R7 - How can we make sure we don't accidentally drop support for old versions? - counter-question: for how long do we want to keep supporting old OSGi/Java versions? ---
