Re: New version has switched build system to Maven - any hint how to resolve dependencies?
----- Mail original -----
> De: "andreas" <andreas@an3as.eu>
> À: "Debian Java List" <debian-java@lists.debian.org>
> Cc: "debian-med" <debian-med@lists.debian.org>, "Afif Elghraoui" <afif@debian.org>
> Envoyé: Mardi 29 Janvier 2019 10:20:48
> Objet: Re: New version has switched build system to Maven - any hint how to resolve dependencies?
> Hi Emmanuel,
>
> On Mon, Jan 28, 2019 at 09:15:49PM +0100, Emmanuel Bourg wrote:
>> No no no it has to work, otherwise you'll run into many other issues...
>
> Ahhh, another very helpful hint. I was running mh_make now and was
> merging its results in. That was very enlightening and saved me some
> stupid patches I did before just since I was to stupid to understand
> maven-helper.
>
>> > [ERROR] Failed to execute goal on project artemis: Could not resolve
>> > dependencies for project uk.ac.sanger:artemis:jar:18.0.1: The following
>> > artifacts could not be resolved: org.apache.xmlgraphics:batik-codec:jar:1.9.1,
>> > org.apache.xmlgraphics:batik-dom:jar:1.9.1,
>> > org.apache.xmlgraphics:batik-ext:jar:1.9.1,
>> > org.apache.xmlgraphics:batik-svggen:jar:1.9.1,
>> > org.apache.xmlgraphics:batik-util:jar:1.9.1, com.ibatis:ibatis:jar:2.3.4.726,
>> > cglib:cglib-nodep:jar:2.2, com.sshtools:j2ssh-core:jar:0.2.9,
>> > org.emboss:jemboss:jar:1.0, org.biojava:biojava:jar:1.6,
>> > com.github.broadinstitute:picard:jar:2.18.14,
>> > org.evosuite:evosuite-standalone-runtime:jar:1.0.6,
>> > org.mockito:mockito-core:jar:2.23.0: Cannot access central
>> > (https://repo.maven.apache.org/maven2) in offline mode and the artifact
>> > org.apache.xmlgraphics:batik-codec:jar:1.9.1 has not been downloaded from it
>> > before. -> [Help 1]
>>
>> ...like this one :)
>
> On the other hand I think there are some remaining packages that are
> not featuring proper maven helper. So I'm now remaining with:
>
>
> [INFO] ------------------------< uk.ac.sanger:artemis >------------------------
> [INFO] Building Artemis 18.0.1
> [INFO] --------------------------------[ jar ]---------------------------------
> [WARNING] The POM for com.ibatis:ibatis:jar:debian is missing, no dependency
> information available
> [WARNING] The POM for com.sshtools:j2ssh-core:jar:debian is missing, no
> dependency information available
> [WARNING] The POM for org.emboss:jemboss:jar:debian is missing, no dependency
> information available
> [WARNING] The POM for org.biojava:biojava:jar:debian is missing, no dependency
> information available
> [WARNING] The POM for com.github.broadinstitute:picard:jar:debian is missing, no
> dependency information available
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 0.450 s
> [INFO] Finished at: 2019-01-29T08:29:42Z
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal on project artemis: Could not resolve
> dependencies for project uk.ac.sanger:artemis:jar:18.0.1: The following
> artifacts could not be resolved: com.ibatis:ibatis:jar:debian,
> com.sshtools:j2ssh-core:jar:debian, org.emboss:jemboss:jar:debian,
> org.biojava:biojava:jar:debian, com.github.broadinstitute:picard:jar:debian:
> Cannot access central (https://repo.maven.apache.org/maven2) in offline mode
> and the artifact com.ibatis:ibatis:jar:debian has not been downloaded from it
> before. -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
>
>
> which are less issues but the according JARs are definitely inside Debian:
>
> com.ibatis:ibatis:jar:debian -> libibatis-java
> com.sshtools:j2ssh-core:jar:debian -> libj2ssh-java
> org.emboss:jemboss:jar:debian -> jemboss
> org.biojava:biojava:jar:debian -> libbiojava-java
> com.github.broadinstitute:picard:jar:debian -> picard-tools
last 2 are build respectivly with ant and gradle, not maven, reason why they do not expose any maven stuff. Nothing done by build-system.
But indeed we can manually (debian side) add some maven stuff to make it maven compliant.
We need to add some pom related files and copy files to usr/share/maven.... directories. Don't know what maven-helper can do to help us with this.
I think I will need to read maven-helper doc to see what can be done.
>
> While the latter three are in possession of the Debian Med team and I'm
> willing to add proper maven metadata to enable correct detection for the
> future, I think there are some replacement rules which would let the
> package build. Unfortunately I never have understand these
> substitutions done in debian/maven.rules and I wonder whether some kind
> soul can provide me with a patch for the said packages.
>
> Kind regards
>
> Andreas.
>
> --
> http://fam-tille.de
Reply to: