Thanks, I didn't know that. In this case I cancel only the vote for JCR Oak Repository Server 1.1.2.
The vote for JCR Resource 2.8.2 is not affected and can continue. Regards Julian On Tue, Nov 15, 2016 at 11:45 AM, Carsten Ziegeler <[email protected]> wrote: > Julian Sedding wrote >> Is it possible if to release only part of the staging repository? If >> so we can continue the vote for JCR Resource. > > Yes, you can remove files from staging and therefore remove the oak > artifacts only, keeping jcr.resource there > > Carsten > >> >> Regards >> Julian >> >> On Tue, Nov 15, 2016 at 11:23 AM, Carsten Ziegeler <[email protected]> >> wrote: >>> Julian Sedding wrote >>>> Hi all >>>> >>>> I will cancel this vote. In an offline discussion with Bertrand and >>>> Carsten we concluded that the LoginAdminWhitelist, that is a private >>>> implementation detail of the Oak Server bundle in the package under >>>> vote, would be better moved to JCR Base, so that any implementation of >>>> its AbstractSlingRepository(Manager) can benefit from this feature >>>> using the same configuration PID. >>>> >>>> Releasing this build of the Oak Server bundle would "publish" a >>>> configuration PID, which would need to be changed in the next release. >>>> Therefore I prefer cancelling this vote. >>>> >>>> Thanks to everyone who voted already and sorry for the inconvenience. >>>> >>> Could we continue the vote for jcr.resource ? >>> >>> >>> Carsten >>> >>> >>> >>> >>> -- >>> Carsten Ziegeler >>> Adobe Research Switzerland >>> [email protected] >>> >> > > > > > -- > Carsten Ziegeler > Adobe Research Switzerland > [email protected] >
