Updating the Sling Parent POM

When to use

Use when the user asks to upgrade the Sling parent POM version in their project.

Instructions

• run a full Maven build with the clean verify. Use the Java version required by the current parent pom version. If the build fails abort execution and inform the user of the root cause. Do not proceeed, otherwise it is impossible to validate the parent pom upgrade.
• check if any known issues with workarounds exist but to do not remove them
• identify the current version of the Sling parent POM in the user's project
• determine the next available version, typically incrementing by 1. For example, if the version is '22' the next version would be '23'
• update the parent pom version
• run a full Maven build with the clean verify goals using the Java version required by the new parent pom version.
• apply additional verification steps as needed if the specific version requires it
• if workarounds were present before updating the parent pom version, check if they can be removed. If they are needed add them back

Do not touch the git repository state - no staging/unstaging, no commits, no pushes.

Java versions

Different parent pom versions require different Java versions. This is listed in the table below. If building with a certain Java version is needed, use the following commands:

• Java 8: mvn8
• Java 11: mvn11
• Java 17: mvn17
• Java 21: mvn21

Parent POM Version	Java Version(s)	Additional fixes needed
22	8	None
23	8	rat-disable
24	8	None
25	8	None
26	8	None
27	8	osgi-r6,servlet-3
28	8	None
29	8	None
30	8	None
31	8	osgi-annotations

Additional fixes

See the following reference files for additional fixes needed to update to a specific parent pom version.

• rat-disable: rat-disable.md
• osgi-r6: osgi-r6.md
• servlet-3: servlet-3.md
• osgi-annotations: osgi-annotations.md

Workarounds

• rat-enable: rat-enable.md