Ccscsce@÷@÷e@
÷se""÷csse,,ec,scce,se,cse,se,se,cse,csse,ccsce,ssse,cssce,se,csce,scce,e,cscc,sce,csccssess@
÷÷@@ßeéwrŕrrrŕ
On Mon, 24 Jun, 2024, 19:00 stefan-egli (via GitHub),
wrote:
>
> stef
> Am 30.08.2022 um 09:28 schrieb Marcel Reutegger:
> > Hi Arun,
> >
> > On 29.08.22, 09:05, "Arun Ram" wrote:
> >> I have checked the classic jackrabbit . Here i dont see the problem.
> >> In classic jackrabbit InternalVersionHistoryImpl[1] re
Hi Marcel,
> This also sounds reasonable. Did you check the behaviour of classic
> Jackrabbit? I think it would be good to have consistent behaviour for
> classic Jackrabbit and Oak.
I have checked the classic jackrabbit . Here i dont see the problem.
In classic jackrabbit InternalVersionHistoryIm
Hi All,
We have encountered a behavior of versionStorage and versionLabels which I
think is bug.
*Current behavior:*
1. Create a node and make it *versionable*
2. Now create more than two versions (for example two version is *1.0*
and *1.1* respectively)
3. Now add label at versio
