Apfloat is split into several modules. One of them is a wrapper for jscience.

Nor jscience nor its dependency, javolution, are currently in Debian, although
there were packaging attempts (to date, libjavolution-java is indeed
ready). Yet, the last released version of jscience (4.3.1) depends on an old
version of javolution (which is now 6.0.0), and there has been many non
backward-compatible ABI changes between the last releases of javolution.
For this reason, we cannot currently package libjscience-java.

Yet, I have written to upstream developer Mikko Tommila and we came to the
conclusion that the apfloat-jscience module can be deactivated. It is
independent of the remaining of the package.
If a new version of jscience is released in the future, there might be worse
trying to package it and activating apfloat-jscience again.

 -- Pierre Gruet <pgt@debian.org>  Sun, 26 July 2020 13:44:30 +0200


The tests of the apfloat module began to fail (https://bugs.debian.org/1086280)
as they create *.ap backup files and their clearing relies on a Java shutdown
thread. Apparently this stopped working under some conditions and tests fail as
they attempt to create already existing .ap files.

For this reason, I have introduced a "listener" artifact which aims to be a
test listener executed after each of them to clear remaining .ap files before
any overwriting. This artifact must not be shipped inside the binary package,
and the tests should not be run in parallel to avoid accidental removals of .ap
files created by other tests running simultaneously.

 -- Pierre Gruet <pgt@debian.org>  Tue, 26 Nov 2024 07:41:39 +0100
