Can't we simply release the parent pom? As this is not really an artifact which is used by our users, we could even do this with a quick vote (24h period).
Carsten Oliver Lietz wrote > On Tuesday 29 May 2018 19:30:51 Konrad Windszus wrote: >> Found it, it was tracked in >> https://issues.apache.org/jira/browse/INFRA-15815 >> <https://issues.apache.org/jira/browse/INFRA-15815>. > > The feedback from infra was quite disappointing. > > Robert, can we work around this limitation by building parent HEAD before > each > build (and using a local per-build Maven repo)? > > Regards, > O. > >>> On 29. May 2018, at 19:24, Konrad Windszus <[email protected]> wrote: >>> >>> Hi, does anyone have any idea, why the Jenkins cannot resolve the latest >>> parent SNAPSHOT >>> (https://builds.apache.org/view/S-Z/view/Sling/job/sling-org-apache-sling >>> -servlets-annotations-it-1.8/3/ >>> <https://builds.apache.org/view/S-Z/view/Sling/job/sling-org-apache-sling >>> -servlets-annotations-it-1.8/3/>)? Is the snapshot repo being added in the >>> Jenkins' settings.xml? >>> I remember vaguely an issue (that was also raised with INFRA) with that >>> but I could not find any references. Does anyone have a hint? >>> >>> If we really have a limitation here, I would like to document that at >>> https://cwiki.apache.org/confluence/display/SLING/Sling+Jenkins+Setup >>> <https://cwiki.apache.org/confluence/display/SLING/Sling+Jenkins+Setup> >>> >>> Thanks, >>> Konrad > -- Carsten Ziegeler Adobe Research Switzerland [email protected]
