Juri Leino

@ahenket `mvn clean` should do the trick (If you have data in that working directory, make a backup first).

@dizzzz you are right that is way easier for one-off tests

Yep, that is still to be done. Maven Central has changed their release process and even though all artifacts were uploaded the new interface does not allow us to release...

Well, then I might need to open a ticket with their support because I cannot access the staging interface anymore to release the uploaded artifacts.

@eduarddrenth Oh thank you I will definitely have a look. I can't change the setup for a version that is already released but we will need to change it for...

Thanks for your issue report. We are, in fact, aware of that and another member of the community has analysed the performance of `util:expand` in detail. We will share this...

@dizzzz are you sure about the `XMLRPC` label? I can remove collections using XMLRPC without an issue.

Can be reproduced. exist version 5 is affected.

I just found this very old issue reporting the same problem https://github.com/eXist-db/exist/issues/1064

@nverwer thanks for your exhaustive bug report. Have you, by any chance, checked if basex does observe this option regardless of module loading mechanism?