[Debian-med-packaging] Bug#895765: How to announce commons.io in gradle build
Andreas Tille
andreas at an3as.eu
Mon Oct 1 20:59:48 BST 2018
Hi,
igv upstream has switched the build system to gradle and provides
specific java9 gradle input file. I probably did not found the most
elegant way to choose this[1] but it should at least work. I wonder
how I should announce common classes that are not found in
...
Compiling with JDK Java compiler API.
/build/igv-2.4.14+dfsg/src/main/java9/module-info.java:96: error: module not found: com.google.common
requires com.google.common;
^
/build/igv-2.4.14+dfsg/src/main/java9/module-info.java:97: error: module not found: commons.io
requires commons.io;
^
/build/igv-2.4.14+dfsg/src/main/java9/module-info.java:98: error: module not found: commons.math
requires commons.math;
^
/build/igv-2.4.14+dfsg/src/main/java9/module-info.java:100: error: module not found: gson
requires gson;
^
/build/igv-2.4.14+dfsg/src/main/java9/module-info.java:110: error: module not found: javafx.base
requires javafx.base;
^
/build/igv-2.4.14+dfsg/src/main/java9/module-info.java:111: error: module not found: javafx.controls
requires javafx.controls;
^
...
since I can not find these in the said *.gradle files and thus have no
idea how to replace the upstream delivered jar file by the Debian
packaged file. The according Build-Depends are (hopefully) properly
set.
Kind regards
Andreas.
[1] https://salsa.debian.org/med-team/igv/commit/1fd85b5d63a43613ee39f7915278e35787438aa2
--
http://fam-tille.de
More information about the Debian-med-packaging
mailing list