Can you try to elaborate which of the changes is responsible for your issue? I think that is related to the updated maven plugins but as I have no access to a Windows based development system I can't test or elaborate which one is responsible.

Can you try to elaborate which of the changes is responsible for your issue?

Basically yes, but if those updates are not critical to security, I'd like to do that later. I currently have a whole series of projects in the line.

This changes contains security fixes too. Not necessary in the used components itself but in the dependencies of the used components.

I looked into the change logs of the changed components and there is not a clear hint of changed functionality.

I found that the error was introduced by the maven-resources-plugin when changing from version 3.2.0 to 3.3.0. However, when I compared the code between the two versions, there is no obvious change that would account for the new behavior. However, the plugin itself includes various dependencies that were increased in that version. Most likely the change originates from one of these.

But this should be confirmed on an other Unix-based system (MacOS/iOS and or an other Linux system maybe?).

I can confirm that Kitodo compiles and runs on MacOS with the the changes in this pull request and the correct local configuration is used. Therefor I am fine with merging this PR when the question with the apparent typo in the comment (see above) has been resolved (@matthias-ronge when you fix the comment, plase seize the opportunity and rebase your branch against the current master!).