You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 19 Next »

PLANNING

Location: diva-e, Berlin Südkreuz
Date: September 28th, 2023
Time: 10:00 - ~16:30/17:00

Participants

Proposed topics

TopicSummaryParticipantsProposed duration
Switch to Jakarta APIs

Unable to render Jira issues macro, execution error.



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?

Features may have dependencies on other Features.

Tie-in discussion: how do we structure our features? We currently have:

  • library : jackson
  • function: validation, maintenance, scripting
  • deployment: docker

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

Unable to render Jira issues macro, execution error.



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



  • No labels