Path: csiph.com!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod From: Andreas Tille Newsgroups: linux.debian.maint.java Subject: Re: Packaging maven-scala-plugin (Was: Help needed for gatk) Date: Mon, 01 Feb 2016 12:20:02 +0100 Message-ID: References: X-Mailbox-Line: From debian-java-request@lists.debian.org Mon Feb 1 11:18:44 2016 Old-Return-Path: X-Amavis-Spam-Status: No, score=-7.001 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, LDO_WHITELIST=-5, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate: -6.1 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.5.23 (2014-03-12) X-Mailing-List: archive/latest/19111 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/20160201111824.GC2206@an3as.eu Approved: robomod@news.nic.it Lines: 65 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: Debian Med Packaging Team X-Original-Date: Mon, 1 Feb 2016 12:18:24 +0100 X-Original-Message-ID: <20160201111824.GC2206@an3as.eu> X-Original-References: <56A0ACD2.4000709@apache.org> <20160127140801.GG19241@an3as.eu> <1453935175.21909.27.camel@gmail.com> <20160128183206.GF2043@an3as.eu> <20160130135904.GG26893@an3as.eu> <56ACCCA9.5040004@apache.org> <20160130170530.GK26893@an3as.eu> <1454187900.16827.5.camel@gmail.com> <20160201085137.GB29773@an3as.eu> <1454324732.4228.22.camel@gmail.com> Xref: csiph.com linux.debian.maint.java:8791 Hi Andrew, On Mon, Feb 01, 2016 at 03:05:32AM -0800, Andrew Schurman wrote: > On Mon, 2016-02-01 at 09:51 +0100, Andreas Tille wrote: > > Thanks for "reading aloud" for me - this might be due to my partial > > blindness for Java problems. :-) > > No worries. Sometimes people overlook the simplest solutions because > they've been tackling a problem for too long.  I'm actually not really worried - just explaining my position to ask in advance for more patience. ;-) > > So I think I need to go on packaging: > > > >     https://maven.apache.org/plugins/maven-toolchains-plugin/  and > >     https://maven.apache.org/plugins/maven-repository-plugin/ > > > > I'm just asking here to make sure that there is no work in progress > > for > > this or that it somehow could be circumvented somehow ... > > Now you've found a more interesting problem. The scala-plugin doesn't > have a direct dependency on these, yet expects them to be there. Seeing > how there have been a few releases with this change, it's unlikely to > be a mishap by the author. Checking `dependency:tree` doesn't list them > either, so we don't need these to be packaged. What this has to mean is > the version of one of the dependencies of the project in debian isn't > correct. A quick search for toolchain in jars of the dependencies show > it's available in maven-core:3.0.4. > > It looks like you're building with maven-core 2.x instead of 3.x since > it was added in 3.x. The debian version of maven-core redirects to 2.x > by default, so you'll need to add a publishedRule to use version 3.x of > maven-core. > > Hopefully that troubleshooting logic will help you. I'm not fully sure. At least I understood that possibly no other packaging task will end up on my desktop. I admit I have no idea how to craft the suggested publishedRule. However, what makes me really suspicious is: $ grep maven.*-core-java maven-scala-plugin_3.2.2-1_amd64.build Selecting previously unselected package libmaven2-core-java. Preparing to unpack .../libmaven2-core-java_2.2.1-24_all.deb ... Unpacking libmaven2-core-java (2.2.1-24) ... Selecting previously unselected package libmaven3-core-java. Preparing to unpack .../libmaven3-core-java_3.3.9-3_all.deb ... Unpacking libmaven3-core-java (3.3.9-3) ... Setting up libmaven2-core-java (2.2.1-24) ... Setting up libmaven3-core-java (3.3.9-3) ... Is there any reason that libmaven2-core-java is implicitly dragged in by other Build-Depends and may be this is creating the problem? Thanks for your patience Andreas. -- http://fam-tille.de