...
Carsten Ziegeler will start the discussion - dev@sling - [RT] Path to Jakarta Servlet Specification
2) Java Version Support
Latest bnd version will support only java 17 on build time
question: should we use build only with java 17 but with source release for java 11?
otherwise we're stuck with old/unmaintained bnd version
running integration test with java 11 gets more complicated
- we also want to add Java 21 as default build for our CIs (it's LTS and GA now) → tracked in
Jira server ASF JIRA serverId 5aa69414-a9e9-3523-82ec-879b028fb15b key SLING-12056
3) JIRA Cleanup
...
- SLF4J 2 is there and some 3rdparty libs start using it exclusively. Although the main API itself is properly maintained and versioned and an be deployed in a backward compatible way, that's not the case for additional helper APIs, which are also used in some places.
- Konrad discussed this a bit with the SLF4J project itself but not with a successful result yet ( https://github.com/qos-ch/slf4j/pull/358 )
Konrad Windszus will come up with a lightweight first proposal
...
- Currently, the "Browsing URL" in the POMs is pointing to GitBox. Those URLs are used by various tooling and humans.
- We should switch it directly to GitHub to easy the discovery process
- The Source Code URLs used for Release Process stick with GitBox
Jira | ||||||
---|---|---|---|---|---|---|
|
9) Create 'apache/sling" entry point on GitHub
- Currently, going to github.com/apache/sling results in a suboptimal user experience, pointing to an obsolete code repository
- Proposal to set up a new "sling" repository mainly consisting of a nice README pointing to the further information and steps
Jira | ||||||
---|---|---|---|---|---|---|
|
10) Enforce CI checks for pull requests?
...
- the XSS bundle is "ugly" and definitly fat (although for reasons). Its used a lot in downstream products and also customer projects, so it's unlikely we can get rid of it. But we should try to reduce the usage of it inside Sling as much as possible, to make it optional for "minimal Sling" distributions.
Carsten Ziegeler will have a look at the remaining usages, for caconfig Stefan Seifert can help - Joerg Hoh will also check over overall list of current sling modules if there are some more which should be marked as archived but are not marked as that currently
Jira | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
13) Cleanup Sling Starter
- we should review the current features for the Starter if we can remove some entries which are now obsolete (e.g. "saaj")
- some of them where introduced for backward compatibility with older Java version and can be dropped probably
Historical references: https://github.com/apache/sling-org-apache-sling-starter/commit/873905db6c0241c4dcc8b016d7b7e2bf60ff7270 /
Jira | ||||||
---|---|---|---|---|---|---|
|
14) Create a shared/reusable Sets of Sonar Rules
...