mreutegg merged PR #675:
URL: https://github.com/apache/jackrabbit-oak/pull/675
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
jsedding merged PR #677:
URL: https://github.com/apache/jackrabbit-oak/pull/677
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
jsedding commented on PR #677:
URL: https://github.com/apache/jackrabbit-oak/pull/677#issuecomment-1227273976
Thanks @dulceanu!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific
Hi Arun,
On 25.08.22, 13:20, "Arun Ram" wrote:
> 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*
>
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
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
mreutegg commented on PR #675:
URL: https://github.com/apache/jackrabbit-oak/pull/675#issuecomment-1227023769
Thanks for the reviews. I added tests you suggested with
https://github.com/apache/jackrabbit-oak/pull/675/commits/8a603d5f4e13304310aa619a56951109e373da4d
--
This is an