update-sling-parent-pom

name	update-sling-parent-pom
description	Use when the user asks to upgrade the Sling parent POM version in their project

Updating the Sling Parent POM

When to use

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

Instructions

• record the current Java and Maven environment with java -version and mvn -version
• run a baseline mvn clean verify if the current checkout is expected to support the current Java version
  • if the baseline build fails only because the current parent POM or project setup requires an older Java version, document that and continue
  • assume the unchanged project would pass with its required Java version; do not switch to version-specific Maven wrappers just to prove the baseline unless the user explicitly asks
  • if the baseline fails for a reason unrelated to the Java version, abort execution and inform the user of the root cause before changing the parent POM
• check if any known workarounds exist, but do not remove them yet
• if other repos in the same workspace/org use the same parent artifact and test patterns (e.g. pax-exam quickstart ITs), check whether one has already been migrated to the target parent version — its pinned test/IT dependency versions are a validated reference point and can save significant troubleshooting
• identify the current version of the Sling parent POM in the user's project
• determine the latest available Sling parent POM version for the applicable parent artifact
  • target the latest available version, not merely the next increment
• check https://cwiki.apache.org/confluence/spaces/SLING/pages/ for an official "Update to Parent NN" migration page covering a version between the current and target (search or ask the user; these pages are not sequentially numbered). Follow any steps it documents that are not already covered by this skill's reference files