Konrad Windszus
Konrad Windszus
We have lots of reports related to that: https://github.com/Adobe-Consulting-Services/acs-aem-commons/issues?q=is%3Aissue%20state%3Aopen%20angular%20vulnerable. If no one steps up to update them nothing will change I guess.
I am gonna merge end of this week, if there is no other feedback.
> as i said before the fact that principals can be exposed on the jackrabbit API is very much an implementation detail of oak and i am not really convinced...
I don't think a default impl in the JR-API module without additional dependencies would work, rather one impl for Oak and one for JR2.
Having a default implementation which just throws an exception is actually worse than requiring any provider. to come up with a reasonable impl. Otherwise semantic versioning becomes useless
@anchela I am gonna merge beginning of next week if I don't receive any further comments here.
@mbaedke Do you plan to pick this up again?
Actually I was wrong, AEM is not using the composite node store during the image build phase. The `seed` mode is just for pre-populating the default store but does not...
The question is how to reliably detect if the last execution of the ACTool was based on a different Cloud Manager build or the same. Potential candidates are: 1. An...
Probably just checking if the previous log was a triggered via `startup_hook_image_build` is enough.