I can prepare a PR for that. Do we already track this in some JIRA issue? Konrad
> On 1. Dec 2025, at 17:25, Stefan Seifert <[email protected]> wrote: > > then let's go with option 1 - it worked for the last years for us. > > stefan > >> -----Original Message----- >> From: Konrad Windszus <[email protected]> >> Sent: Monday, December 1, 2025 5:18 PM >> To: [email protected] >> Subject: Re: CI build with snapshot deps are breaking with Apache Parent >> 35 / Sling Parent 63 >> >> Hi, >> I would strongly suggest to still do it in pom.xml. >> Otherwise every Sling contributor is forced to mingle with the local >> settings.xml potentially to build locally. >> That is IMHO too much friction for very little reason. >> Also otherwise consumers of a SNAPSHOT version cannot resolve SNAPSHOT >> dependencies either. >> >> Therefore I would strongly suggest to just reenable that repo in the >> parent POM with the property. >> Konrad >> >>> On 1. Dec 2025, at 14:29, Robert Munteanu <[email protected]> wrote: >>> >>> Hi Stefan, >>> >>> On Mon, 2025-12-01 at 12:37 +0000, Stefan Seifert wrote: >>>> 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. >>> >>> We could try it and see where it goes and if we find out it's too >>> annoying when doing local development we can go with option 1. >>> >>> Thanks, >>> Robert >>> > >
