Debian Patches
Status for junit5-system-exit/2.0.3-2
| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| 01-disable-java-toolchain.patch | Do not pin a Java toolchain The package builds with the default JDK of the distribution, which Gradle would not be allowed to swap for a provisioned JDK 17, and it ships neither a sources nor a javadoc jar. |
Emmanuel Bourg <ebourg@apache.org> | not-needed | |||
| 02-disable-tests.patch | Disable the test task Gradle gained useJUnitPlatform() in 4.6 only, so the version in Debian cannot run a JUnit 5 suite at all, and debian/rules runs it with the JUnit console launcher instead. The test-logger plugin, which formats the output of the task, is downloaded from the Gradle Plugin Portal and goes with it. . A newer Gradle would let the task run again; the block would then only need its reference to the archive file of the jar adapted, which upstream writes the Gradle 5 way. |
Emmanuel Bourg <ebourg@apache.org> | not-needed | |||
| 03-disable-jacoco.patch | Disable the code coverage The coverage report is of no use to the package: it produces no installed artifact and the tests are run outside Gradle by debian/rules. The jacocolog plugin formatting it is downloaded from the Gradle Plugin Portal anyway, and the report configuration relies on the lazy properties of Gradle 6.1. |
Emmanuel Bourg <ebourg@apache.org> | not-needed | |||
| 04-disable-publishing.patch | Disable the publication to Maven Central The package publishes nothing: jreleaser and the signing keys read from the environment are release tooling, and the POM installed in /usr/share/maven-repo is generated by gradle-debian-helper rather than by maven-publish, which the build therefore does not need at all. |
Emmanuel Bourg <ebourg@apache.org> | not-needed | |||
| 05-project-version.patch | Take the project version from VERSION.txt gitBranch() runs git rev-parse in the build directory to tell a release from a snapshot, and throws when it finds no repository, which is what the tarball ships. Short-circuiting it to the release branch leaves the version read from VERSION.txt, and the packaging already relies on that file matching the upstream version since debian/rules symlinks the jar under that name. |
Emmanuel Bourg <ebourg@apache.org> | not-needed | |||
| 06-gradle-compatibility.patch | Adapt the build script to Gradle 4.5 because() and the typed task accessors of the tasks block arrived in Gradle 4.6, the vararg form of Manifest.attributes() and archiveVersion in Gradle 5. because() is stubbed out rather than removed, which leaves the upstream declarations untouched; the javadoc task is commented out instead of adapted, it also reads the toolchain that 01-disable-java-toolchain.patch disables. . Nothing here is a packaging choice, so the patch goes as a whole once the Gradle version in Debian catches up. |
Emmanuel Bourg <ebourg@apache.org> | not-needed |