THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
| Topic | Summary | Participants | Proposed duration | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Switch to Jakarta APIs |
| ||||||||||||||
| Is Sling becoming too fat? | In e.g. Sling XSS there is a considerable increase in dependencies. | ||||||||||||||
| Is maintaining proper features (OSGi, Karaf) worth the effort? | In 936eb9f a bundle was added to feature models-jacksonexporter for XSS. Could we use dependencies to create and manage proper features? Is it supported by OSGi Features? Tie-in discussion: how do we structure our features? We currently have:
There is also a question of whether the healthcheck webconsole bundle belongs in the healthcheck or the webconsole feature. Or maybe in a healthcheck-webconsole feature? | ||||||||||||||
| Adopt SLF4J 2.x |
| ||||||||||||||
| Enforcing CI checks for pull requests | Classify modules and enfore specific CI checks, based on module maturity/risk profile. | ||||||||||||||
| Migrate Sling Models/CAConfig Integration Tests to Sling 12/Feature Model | Integration tests are currently broken or use very outdated Sling Starter. Goal would be to switch to Sling 12+Feature Module and move the integration tests in the actual codebase of the implementation classes, no separate codebase for ITs. see also discussion in https://lists.apache.org/thread/fwwnb2hyqf2t2ko4pfmhhxd7wrhwmbh6 WIP in https://github.com/apache/sling-org-apache-sling-models-impl/pull/46 | ||||||||||||||
| Required Java Versions for Building and Running | Bnd 7.x requires Java 17+ (https://github.com/bndtools/bnd/wiki/Changes-in-7.0.0) Drop Java 8 x support at run time (
Drop also Java 11 support at run time? |
...