David Buchmann

i can reproduce the failing unit tests with NodeHelperTest looking at the NodeHelper, i can't imagine why this has worked in the past. you use `'uuid'` as node id, instead...

i think the strict typing refactorings make visible what before would have been a fatal error when trying to run it, but did not break the container. can you try...

i fixed `You have requested a non-existent parameter "doctrine_phpcr.jackrabbit_jar".` in https://github.com/jackalope/jackalope-jackrabbit/pull/185 and https://github.com/doctrine/DoctrinePHPCRBundle/pull/395 are any of the other failures related to regressions in phpcr/jackalope?

that is weird indeed. what did change is that doctrine and symfony prefer attributes over annotations. the stack trace is indicating that this is about doctrine bundle (the orm thing)...

there also seems to be a setup issue with `An exception occurred while executing a query: SQLSTATE[42P01]: Undefined table: 7 ERROR: relation "phpcr_namespaces" does not exist` i am not sure...

> there also seems to be a setup issue with `An exception occurred while executing a query: SQLSTATE[42P01]: Undefined table: 7 ERROR: relation "phpcr_namespaces" does not exist` > > i...

the typeerror: phpcr always had the phpdoc of `@return \Iterator`. phpcr-api-tests is not explicitly testing that, but [implicitly assuming it](https://github.com/phpcr/phpcr-api-tests/blob/f22ed0e882debf1c98da52a2b9262ec6dc8b459c/inc/BaseCase.php#L205). i feel that relaxing the phpcr interface to allow any...

> it does install phpcr bundle 2.5 which is not compatible with jackalope 2 but phpcr bundle does not define its requirements for jackalope. i could add a conflict to...

> We would need to add conflict to ^2.5 version and sulu then would require to require atleast that version that way it would work, as composer then can not...

yay, that looks pretty green now \0/ looks like whats left now is mainly about the added strict typing in upstream libraries that makes phpstan report missing checks for `null`...