On 2024/02/23 16:15:06 Julian Reschke wrote: > > Can the check-release.sh be updated, please? > > Right now, we can't. a) Because we share the script with Oak (which is > known not to have reproducable builds),
ok, I'll work on it > >> and the environment doing the release fixed? > > > > If I understood what the problem is I'll be happy to fix it. > > ... > > So it seems that the weird permissions are caused by the fact that my > WSL instance uses a local maven repo mounted from a Windows FS. Once I > move to a Linux-native repo, the permissions are different. thank you for the explanation of the root cause: this is the first time I see this one, with some good surprises (newline) and some bad ones (executable) > I can try this for the next release (and the downside of course is disk > space impact on the release machine). It would be better if we could > tell the plugin generating the WAR file to normalize the permissions; > otherwise the build will always depend on the setting in the local maven > repo. now that I understand why it is needed, I suppose I can add the feature to maven-war-plugin: I'll work on it and propose a PR to jackrabbit thanks for the feedback changing my vote to +1, given there is a clear explanation (having a plan to solve is even better) Best regards, Hervé
