On 29. 7. 2026 11:08, Daniel Sahlberg wrote:
Den mån 13 juli 2026 kl 13:38 skrev Evgeny Kotkov via dev
<[email protected]>:
The 1.15.0-rc3 release artifacts are now available for
testing/signing.
Please get the tarballs from
https://dist.apache.org/repos/dist/dev/subversion
and add your signatures there.
Thanks!
As noted in the "JavaHL jar file containing class files for unit
tests" thread[1], the javahl bindings can only be installed if built
with junit.
The following sniped it from the other thread, done on trunk but the
failure is the same on 1.15.x.
[[[
$ /bin/sh autogen.sh
$ ./configure --prefix=/dev/shm/svn/trunk --without-apxs
--without-swig --without-swig-{perl,python,ruby} --enable-javahl
--with-jdk=/usr/lib/jvm/java-11-openjdk-amd64 --without-junit
PYTHON=/usr/bin/python3
$ make -j$(nproc) all
$ make javahl
$ find subversion/bindings/javahl -name '*.class' | wc -l
277
$ find subversion/bindings/javahl -name '*Test*.class' | wc -l
0 #==> tests/**/*.java are compiled yet.
$ make install
$ make install-javahl # Why this task builds tests/**/*.java?
...
/dev/shm/subversion-trunk/subversion/bindings/javahl/tests/org/tigris/subversion/javahl/BasicTests.java:1708:
error: cannot find symbol
assertEquals("wrong revision from commit",
^
symbol: method assertEquals(String,long,int)
location: class BasicTests
/dev/shm/subversion-trunk/subversion/bindings/javahl/tests/org/tigris/subversion/javahl/BasicTests.java:1756:
error: cannot find symbol
assertEquals("wrong revision from update",
^
symbol: method assertEquals(String,long,int)
location: class BasicTests
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
100 errors
]]]
If built with --with-junit the install-javahl target succeed.
It is caused by r1934378 which backported r1933892.
As noted in the other thread, Ubuntu and Fedora seems to build with
--with-junit and FreeBSD builds without.
I'm not sure if this is serious enough to block the release (in which
case we might want to revert r1934378) or if it is enough to note as a
known issue. It will cause issues for FreeBSD but it is quite easy to
work around.
As I mentioned elsewhere, changes in build requirements are pretty much
normal for a .0 release. I would approve of making --with-junit
mandatory if JavaHL is enabled.
-- Brane