Package: libapfloat-java / 1.15.0-1

Metadata

Package Version Patches format
libapfloat-java 1.15.0-1 3.0 (quilt)

Patch series

view the series file
Patch File delta Description
managing_test_dependency.patch | (download)

apfloat-aparapi/pom.xml | 2 1 + 1 - 0 !
apfloat-jscience/pom.xml | 2 1 + 1 - 0 !
pom.xml | 2 1 + 1 - 0 !
3 files changed, 3 insertions(+), 3 deletions(-)

 substituting old type "test-jar" with classifier "tests".
 Discussed on https://github.com/mtommila/apfloat/issues/13, this seems to be
 a Debian-only issue.
remove_test_that_fails_randomly.patch | (download)

apfloat/src/test/java/org/apfloat/internal/ParallelRunnerTest.java | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 removing a test that randomly fails
 The test testWait fails at random times. I have contacted Mikko Tommila
 (upstream developer), who said that ``that test fails sometimes randomly. I
 suppose it has something to do with the internals of Java's ForkJoinPool. The
 test is by no means critical, you can remove it. The idea of the test is to
 test that the ParallelRunner uses parallel threads optimally. But sometimes
 ForkJoinPool creates more threads that you would expect it needs to, I don't
 know why. And then the test can randomly fail. But it should only test optimal
 thread allocation, not correctness of functionality.''
 I am thus following the advice and removing the test.
changing_names_of_generated_jars.patch | (download)

apfloat-applet/pom.xml | 2 1 + 1 - 0 !
apfloat-calc/pom.xml | 2 1 + 1 - 0 !
apfloat-samples/pom.xml | 2 1 + 1 - 0 !
3 files changed, 3 insertions(+), 3 deletions(-)

 changing names of jars to conform to debian java policy
no_generated_manifest.patch | (download)

apfloat-aparapi/pom.xml | 5 0 + 5 - 0 !
apfloat-calc/pom.xml | 5 0 + 5 - 0 !
apfloat-jscience/pom.xml | 5 0 + 5 - 0 !
apfloat/pom.xml | 5 0 + 5 - 0 !
4 files changed, 20 deletions(-)

 manifest generation from upstream pom files does not work as it
 seems to rely on some plugins we don't have in Debian. Turning it off, as the
 Debian Java toolchain will generate them afterwards anyway.
use_custom_test_listener.patch | (download)

apfloat/pom.xml | 17 17 + 0 - 0 !
pom.xml | 8 7 + 1 - 0 !
2 files changed, 24 insertions(+), 1 deletion(-)

 handling a listener artifact to remove .ap files created by tests
 each time one of them terminates. This is to avoid a bug that began showing up
 on Debian and that does not seem to be reproduciable outside.