Hi, Updating the parent pom version in Sling modules is one task that usually gets left behind. We have many modules, the work is not that rewarding and sometimes very tedious - for instance migrating from the Felix SCR annotations to the official OSGi ones.
To make things simpler I have started an experiment in the whiteboard - using agent skills [1] to upgrade the parent pom version. Installation instructions are in the whiteboard [2] ; you need old Java versions around to run builds on old parent versions but once that is done the skill is easy to execute. I open up a coding agent and tell it 'update the parent pom version'. The skill currently supports parent versions 22 through 34 ; 35 is still a work in progress. I've pushed the results of updating the org.apache.sling.jcr.js.nodetypes bundle using only this skill to [3]. It's not the most complex module of all but I think it's still a good test bed. Is there interest in adding this kind of support to Sling? It would be great if people would take this for a spin and see how it works for different modules. Thanks, Robert [1]: https://agentskills.io/ [2]: https://github.com/apache/sling-whiteboard/tree/master/skills/ [3]: https://github.com/apache/sling-org-apache-sling-jcr-js-nodetypes/compare/experiment/parent-pom-update-skills?expand=1
