On Fri, Nov 9, 2018 at 4:22 PM Emmanuel Bourg <ebo...@apache.org> wrote: > > Le 09/11/2018 à 16:16, Mathieu Malaterre a écrit : > > > Odd, this does not seems to work for me: > > > > https://salsa.debian.org/java-team/fop/blob/wip-2.3/debian/rules > > Sorry I forgot "--", it's "dh_auto_build -- -X package -DskipTests",
Odd, this is even worse: [INFO] ------------------------------------------------------------------------ [ERROR] Unknown lifecycle phase "libfop-java". You must specify a valid lifecycle phase or a goal in the format <plugin-prefix>:<goal> or <plugin-group-id>:<plugin-artifact-id>[:<plugin-version>]:<goal>. Available lifecycle phases are: validate, initialize, generate-sources, process-sources, generate-resources, process-resources, compile, process-classes, generate-test-sources, process-test-sources, generate-test-resources, process-test-resources, test-compile, process-test-classes, test, prepare-package, package, pre-integration-test, integration-test, post-integration-test, verify, install, deploy, pre-clean, clean, post-clean, pre-site, site, post-site, site-deploy. -> [Help 1] org.apache.maven.lifecycle.LifecyclePhaseNotFoundException: Unknown lifecycle phase "libfop-java". You must specify a valid lifecycle phase or a goal in the format <plugin-prefix>:<goal> or <plugin-group-id>:<plugin-artifact-id>[:<plugin-version>]:<goal>. Available lifecycle phases are: validate, initialize, generate-sources, process-sources, generate-resources, process-resources, compile, process-classes, generate-test-sources, process-test-sources, generate-test-resources, process-test-resources, test-compile, process-test-classes, test, prepare-package, package, pre-integration-test, integration-test, post-integration-test, verify, install, deploy, pre-clean, clean, post-clean, pre-site, site, post-site, site-deploy. at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.calculateLifecycleMappings (DefaultLifecycleExecutionPlanCalculator.java:248) > > > Right. That is also my guess but since I fail to understand which > > version is being used during the build I did not know how to proceed. > > fop currently depends on libqdox-java. Try switching to libqdox2-java > and updating the Maven rules with: > > com.thoughtworks.qdox qdox * s/.*/2.x/ * * This one was there already: https://salsa.debian.org/java-team/fop/blob/wip-2.3/debian/maven.rules#L2