Re: ACL on versioned node

2018-11-02 Thread Marco Piovesana
Hi Angela, thanks for the clarification, I thought the access control content was versioned alongside the node. If you don't mind me asking I have another question though (that might be a little off topic): why is required to version a node to change its access control information if the access

Re: ACL on versioned node

2018-11-02 Thread Alex Deparvu
Hi, Could this be related to adding the "rep:AccessControllable" mixin if it doesn't exist on that specific node? (The AccessControlManagerImpl will update the mixins property in the case it is not there.) It fits with the examples: > If I create the first version of a node *after* adding an

OAK-7511 (nullability annotations) vs Oak 1.8.*

2018-11-02 Thread Julian Reschke
Hi there, so we made the switch to the Jetbrains annotations in trunk some time ago (July). Doing so required a micro version update, because the annotations are considered part of the API. We now have an issue with the backport for OAK-7741 in 1.8, which would *also* change the version

Re: ACL on versioned node

2018-11-02 Thread Marco Piovesana
Hi Angela, let me try to rephrase my followup question. I have a versioned node and I need to change the permissions a user has on that node. If I try to modify the access control without checking-out the node I got the error: *OakVersion0001: Cannot change property jcr:mixinTypes on checked in

Re: ACL on versioned node

2018-11-02 Thread Angela Schreiber
Hi Marco Regarding your original question I found, that I was actually mistaken :-) See OAK-6015 for the reason why IGNORED nodes are treated differently. Not sure thought I understand your followup question... you don't need to make a node versionable or version it in order to place/edit

Re: OAK-7511 (nullability annotations) vs Oak 1.8.*

2018-11-02 Thread Angela Schreiber
Hi Alex I don't want to single out OAK-7741 and I know that there are sometimes compelling reasons to backport even improvements. Just want to avoid future troubles as I experienced it it in the external authentication code base with backports of improvements (one time even ending up with

Re: OAK-7511 (nullability annotations) vs Oak 1.8.*

2018-11-02 Thread Alex Deparvu
Hi, I think it's easy to single out OAK-7741 as the source of the issues, when in fact the question is really about all the classes affected by the OAK-7511 change. As it stands now, none of them are backportable to 1.8 due to the exact same issues as OAK-7741: the annotation change will trigger