Hi,
On Mon, Aug 20, 2018 at 12:39:21AM +0200, Emmanuel Bourg wrote:
> > do you have any hint how to deal with this issue?
>
> The actual error is:
>
> [javac]
> /build/1st/jmodeltest-2.1.10+dfsg/src/main/java/es/uvigo/darwin/jmodeltest/ModelTestService.java:28:
> error: package parser does not exist
> [javac] import parser.ParseException;
> [javac] ^
> [javac]
> /build/1st/jmodeltest-2.1.10+dfsg/src/main/java/es/uvigo/darwin/jmodeltest/ModelTestService.java:29:
> error: package converter does not exist
> [javac] import converter.Converter;
> [javac] ^
> [javac]
> /build/1st/jmodeltest-2.1.10+dfsg/src/main/java/es/uvigo/darwin/jmodeltest/ModelTestService.java:30:
> error: package converter does not exist
> [javac] import converter.DefaultFactory;
> [javac] ^
> [javac]
> /build/1st/jmodeltest-2.1.10+dfsg/src/main/java/es/uvigo/darwin/jmodeltest/ModelTestService.java:31:
> error: package converter does not exist
> [javac] import converter.Factory;
> [javac] ^
>
> There is an issue with a dependency (alter-sequence-alignment maybe?),
> the Java version isn't to blame here.
Good catch. The latest upstream version of alter-sequence-alignment has
split these to an additional alter-lib.jar and the time of the build
failure of jmodeltest correlates with the upload of
alter-sequence-alignment 1.3.4-1. But now the question is: How to
teach the jmodeltest build system to use alter-lib.jar. I think adding
it to debian/manifest[1] is needed to *run* jmodeltest but it surely
does not help at build time. I have not found any place where the
build system specifies the needed jars. :-(
Any hint?
Kind regards
Andreas.
[1]
--
http://fam-tille.de
