-1 on that proposal. Why revert the plugin updates if there is an easy fix? Managing each plugin update in individual JIRA/commit is an effort I am not willing to invest. Also this wouldn’t have made this issue any easier to detect. From my perspective backporting the plugin updates as a whole to 1.22 should be no real problem.
Konrad > Am 16.12.2022 um 06:55 schrieb Julian Reschke <julian.resc...@gmx.de>: > > On 16.12.2022 04:53, Nitin Gupta wrote: >> FYI, the release is currently blocked on >> https://issues.apache.org/jira/browse/OAK-10032. >> >> Regards, >> Nitin > > My proposal is to back out the change and make that release. > > Once that is done, we can and should address the individual tasks in > that commit separately. In particular, avoiding the whole issue of > having to use the ant maven plugin to copy a file might be best (as > suggested by Konrad), > > Separating these issues into smaller tasks will be useful when we decide > which of these to backport to 1.22. > > Best regards, Julian >
