as discovered by robert in [1], we have backward-incompatible change in our parent POM 63 (inherited from the latest Apache Parent POM 35): in the newest release, the apache snapshot maven reposistories are not active in the build by default, effectively breaking the build everywhere where those snapshot repos are not activated by default in local maven settings configuration.
this effects all our Jenkins builds which are updating to Parent 63. there are two ways to fix this: 1. fix this in our parent POM by enabling the profile 'use-apache-snapshots' by default - this restores the previous behavior 2. ensure that the apache snapshot repository are properly configured in all build environments, esp. our Jenkins builds and keeping the snapshot repositories out of the POMs. personally, I prefer to not putting references to any maven repositories in POMs, as this can "poison" your builds chains with references to repositories you cannot easily get rid of if you want to load the artifacts from other repositories. but usually that's not a big issue if it relates only to snapshot repositories, as it is the case with the 'use-apache-snapshots' profile. so i'm also fine with approach #1 as it is the easiest solution for us, and is in line with what configuration we have used for years. stefan https://github.com/apache/sling-org-apache-sling-starter-integration-tests/pull/37#issuecomment-3596273861
