[From nobody Tue Oct 27 13:51:06 2026
Received: (at submit) by bugs.debian.org; 12 Dec 2017 12:44:01 +0000
X-Spam-Checker-Version: SpamAssassin 3.4.1-bugs.debian.org_2005_01_02
 (2015-04-28) on buxtehude.debian.org
X-Spam-Level: 
X-Spam-Status: No, score=-14.3 required=4.0 tests=BAYES_00,HAS_PACKAGE,
 SPF_SOFTFAIL,XMAILER_REPORTBUG,X_DEBBUGS_CC autolearn=ham autolearn_force=no
 version=3.4.1-bugs.debian.org_2005_01_02
X-Spam-Bayes: score:0.0000 Tokens: new, 10; hammy, 95; neutral, 36; spammy, 1.
 spammytokens:0.953-+--H*r:bugs.debian.org
 hammytokens:0.000-+--H*M:reportbug, 
 0.000-+--H*MI:reportbug, 0.000-+--H*x:7.1.7, 0.000-+--H*UA:7.1.7,
 0.000-+--H*x:reportbug
Return-path: <ebourg@apache.org>
Received: from cirrus.ariane-software.com ([5.196.81.173]
 helo=icare.ariane-software.com)
 by buxtehude.debian.org with esmtp (Exim 4.89)
 (envelope-from <ebourg@apache.org>) id 1eOjuj-0002H0-9H
 for submit@bugs.debian.org; Tue, 12 Dec 2017 12:44:01 +0000
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Emmanuel Bourg <ebourg@apache.org>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: maven-debian-helper: Support modules with the same dependency but
 different scopes
Message-ID: <151308263919.22052.14955722063389276537.reportbug@icare.ariane-software.com>
X-Mailer: reportbug 7.1.7
Date: Tue, 12 Dec 2017 13:43:59 +0100
X-Debbugs-Cc: ebourg@apache.org
Delivered-To: submit@bugs.debian.org

Package: maven-debian-helper
Version: 2.2.8
Severity: normal

When a multi-modules project has two modules sharing the same dependency
but with different scopes, maven-debian-helper gets confused and doesn't
use the right dependency group for the associated packaged.

For example with activemq/5.15.2-1, the commons-net dependency is optional
in the activemq-client module but mandatory in the activemq-kahadb-store
module. In this case maven-debian-helper believes the dependency is
optional and puts libcommons-net-java in ${maven:OptionalDepends} instead
of ${maven:Depends}. I haven't checked if the dependencies with the
'provided' scope are also affected by this issue.
]