Am 26.02.2021 um 12:14 schrieb Konrad Windszus:
The simplest fix would be to remove the file from the ZIP, and then let
people retry...
Not that easy, as then the checksums and the signature would no longer match...
If you consider this a blocker I guess I have to respin the release...
...
Ack.
So with
--
Index: check-release.sh
===================================================================
--- check-release.sh (revision 46347)
+++ check-release.sh (working copy)
@@ -63,8 +63,8 @@
# https://github.blog/2011-10-20-improved-subversion-client-support/
TAGURL="https://github.com/apache/jackrabbit-filevault/tags/$COMPONENT-$VERSION";
MVN_ARGS=""
- CLEAN_SVN=".gitignore .gitattributes"
- CLEAN_ZIP=""
+ CLEAN_SVN=".gitignore .gitattributes derby.log"
+ CLEAN_ZIP="derby.log"
HASHES="sha1 sha512"
;;
*)
--
the build passes for me, where:
[INFO] Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
[INFO] OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
[INFO] Java version: 1.8.0_221, vendor: Oracle Corporation, runtime:
C:\usr\local\jdk18\jre
[INFO] MAVEN_OPTS: -Xmx2g
I noticed that versions:display-dependency-updates shows a few 2.14.0
references for Jackrabbit, and also ancient versions of
jackson-databind. Not sure whether this is a problem in practice (you
may want to check).
Best regards, Julian
