[From nobody Tue Oct 27 17:53:09 2026 Received: (at submit) by bugs.debian.org; 10 May 2023 15:15:21 +0000 X-Spam-Checker-Version: SpamAssassin 3.4.6-bugs.debian.org_2005_01_02 (2021-04-09) on buxtehude.debian.org X-Spam-Level: X-Spam-Status: No, score=-8.6 required=4.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FOURLA,FREEMAIL_FROM, HAS_PACKAGE,HTML_MESSAGE,MULTALT,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE, SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6-bugs.debian.org_2005_01_02 X-Spam-Bayes: score:0.0000 Tokens: new, 67; hammy, 150; neutral, 156; spammy, 0. spammytokens: hammytokens:0.000-+--bookworm, 0.000-+--X-Debbugs-Cc, 0.000-+--XDebbugsCc, 0.000-+--sk:taint_o, 0.000-+--sk:TAINT_O Return-path: <stanislav.vdimov@gmail.com> Received: from mail-yb1-xb2e.google.com ([2607:f8b0:4864:20::b2e]:62638) by buxtehude.debian.org with esmtps (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_128_GCM:128) (Exim 4.94.2) (envelope-from <stanislav.vdimov@gmail.com>) id 1pwlXE-00FHOL-9U for submit@bugs.debian.org; Wed, 10 May 2023 15:15:21 +0000 Received: by mail-yb1-xb2e.google.com with SMTP id 3f1490d57ef6-b9a6eec8611so36447614276.0 for <submit@bugs.debian.org>; Wed, 10 May 2023 08:15:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1683731716; x=1686323716; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=sYFslMli1ZDgR8H8tdA7vQvY5FZndchWjGV0B3/0DMs=; b=c3exBDwh9JTjsZ7vh7O72EORhJfbBhrHX9k9IFj7ojdCIELwKhahLVyNr0ipMWxYqc lbXawgTSVfix5ra9Z53YwJPc37dJU/BzC38nq2ZoS1udq7BDri/xI2G4RV0kN+EKO8L3 AL8LVUxjcgJxk2umCyV4tKUCMG7pSxrMv0GMFWQbRYZw0EuTM0GxX6g3MfDXnYw5tZUX maZV8wGE6+dJVfScxTNHpdvHkfM3lTDvf7abyKfZAqw0zNjxdvm1Tm2liDP/yZSlxQxz CjrdxNVZfZhz7ANdSVkxij1E6fNmtZXIyIAa7pxOd4d/pcplVxqJnB/k6wKzJfIG6W/e 0C1Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683731716; x=1686323716; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=sYFslMli1ZDgR8H8tdA7vQvY5FZndchWjGV0B3/0DMs=; b=aOtbQrwk2MrTjwt81PW+P8Piz6SsaNf6f2+Sj7M4r3ks4yw8XwG/Q8TU0M6t3oiqAA dLEP1kLzMPnhPuQEARdSIAimiwGpRMSqrFCvK7RPwy9yiZpgb2fF24tSt31e0+bxocju UxPCLfy2PPSHmNL9m3uO6ROaD690vnNPtvAUgK0ROOVgRvQA8xJl+1zdieTI0V7+bDSm eOxYdGmvpW7UkVQvHK0DWOWDgyHUoxE0t6l8nJk3/pYga2ySUIj6tY3oOZ0eavMyVSoL Lfd4DrIT47G7EmTYQQ3hezniWOZz3GHrxujnsSCeprcQoCaP5tq6aiddlw3yTkWCnALp rtGw== X-Gm-Message-State: AC+VfDxqceVjsuqtihXfzE8DzDv300WyjvX8xq4SMh0Jt0iNbbkuZHrm qwzrD2RNkcHcq8b9tDJk8gJn49t2OSg3Cst0vBn3mQnxfp/fBw== X-Google-Smtp-Source: ACHHUZ6Iyuto9sL3qV3ZafjH26aqVh+qLOL5LldZwIEE/EK0bTzfffRMe+A9QrIRbyS3XEYqOqKpmg7DsJ/Q3JnZNoM= X-Received: by 2002:a25:19c1:0:b0:b9d:766d:f72b with SMTP id 184-20020a2519c1000000b00b9d766df72bmr17767595ybz.31.1683731716424; Wed, 10 May 2023 08:15:16 -0700 (PDT) MIME-Version: 1.0 From: Stanislav Dimov <stanislav.vdimov@gmail.com> Date: Wed, 10 May 2023 16:15:05 +0100 Message-ID: <CAKn98Oa5OJMe=X9B0a+dCmZk-Y+gV7rfLRO2aBR-LOnBEEb5iA@mail.gmail.com> Subject: maven-debian-helper: mh_make cannot resolve parent POM when `<version>${revision}</version>` is used To: submit@bugs.debian.org Content-Type: multipart/alternative; boundary="000000000000dac93105fb585678" Delivered-To: submit@bugs.debian.org --000000000000dac93105fb585678 Content-Type: text/plain; charset="UTF-8" Package: maven-debian-helper X-Debbugs-Cc: stanislav.vdimov@gmail.com Version: 2.6 Severity: normal Dear Maintainer, * What led up to the situation? I tried to create a deb package for a maven project I am working on using `mh_make`. * What exactly did you do (or not do) that was effective (or ineffective)? I invoked `mh_make` and started filling in the required information. When I got to the module resolution I was greeted by an error: ``` Analysing model/pom.xml... May 10, 2023 3:33:12 PM org.debian.maven.packager.DependenciesSolver resolveDependencies SEVERE: Error while resolving ./model/pom.xml: Dependency not found com.mycompany.proj:project_name:pom:${revision} May 10, 2023 3:33:12 PM org.debian.maven.packager.DependenciesSolver resolveDependencies SEVERE: org.debian.maven.repo.DependencyNotFoundException: Dependency not found com.mycompany.proj:project_name:pom:${revision} at org.debian.maven.repo.Repository.registerPom(Repository.java:419) at org.debian.maven.packager.DependenciesSolver.resolveDependencies(DependenciesSolver.java:320) at org.debian.maven.packager.DependenciesSolver.resolveDependencies(DependenciesSolver.java:420) at org.debian.maven.packager.DependenciesSolver.solveDependencies(DependenciesSolver.java:260) at org.debian.maven.packager.DependenciesSolver.main(DependenciesSolver.java:922) ``` The way it is set up is that all subprojects use the `${revision}` placeholder to resolve the parent POM's version. I believe this was introduced in maven 3.5. The project builds normally when `mvn package` is invoked. * What was the outcome of this action? `mh_make` crashed * What outcome did you expect instead? `mh_make` to resolve the dependency with the parent pom and continue with the setup. -- System Information: Debian Release: bookworm/sid APT prefers jammy-updates APT policy: (500, 'jammy-updates'), (500, 'jammy-security'), (500, 'jammy'), (100, 'jammy-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.2.6-76060206-generic (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages maven-debian-helper depends on: ii default-jdk 2:1.11-72build2 ii default-jdk-headless 2:1.11-72build2 ii libmaven-clean-plugin-java 3.1.0-1 ii libmaven-compiler-plugin-java 3.8.1-4 ii libmaven-jar-plugin-java 3.1.2-1 ii libmaven-resources-plugin-java 3.1.0-1 ii libmaven-site-plugin-java 3.6-4 ii libplexus-velocity-java 1.2-3.1 ii libsurefire-java 2.22.3-1 ii libxml2-utils 2.9.13+dfsg-1ubuntu0.3 ii maven 3.6.3-5 ii maven-repo-helper 1.10 ii unzip 6.0-26ubuntu3.1 ii velocity 1.7-6 maven-debian-helper recommends no packages. Versions of packages maven-debian-helper suggests: ii apt-file 3.2.2 ii libmaven-javadoc-plugin-java 3.0.1-4 ii licensecheck 3.2.14-2 pn subversion <none> -- no debconf information --000000000000dac93105fb585678 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">Package: maven-debian-helper<br>X-Debbugs-Cc: <a href=3D"m= ailto:stanislav.vdimov@gmail.com">stanislav.vdimov@gmail.com</a><br>Version= : 2.6<br>Severity: normal<br><br>Dear Maintainer,<br><br>=C2=A0 =C2=A0* Wha= t led up to the situation?<br>=C2=A0 =C2=A0 =C2=A0I tried to create a deb p= ackage for a maven project I am working on using<br>`mh_make`.<br><br>=C2= =A0 =C2=A0* What exactly did you do (or not do) that was effective (or<br>= =C2=A0 =C2=A0 =C2=A0ineffective)?<br>=C2=A0 =C2=A0 =C2=A0I invoked `mh_make= ` and started filling in the required information. When<br>I got to the mod= ule resolution I was greeted by an error:<br><br>```<br>Analysing model/pom= .xml...<br>May 10, 2023 3:33:12 PM org.debian.maven.packager.DependenciesSo= lver<br>resolveDependencies<br>SEVERE: Error while resolving ./model/pom.xm= l: Dependency not found<br>com.mycompany.proj:project_name:pom:${revision}<= br>May 10, 2023 3:33:12 PM org.debian.maven.packager.DependenciesSolver<br>= resolveDependencies<br>SEVERE:<br>org.debian.maven.repo.DependencyNotFoundE= xception: Dependency not found<br>com.mycompany.proj:project_name:pom:${rev= ision}<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 at org.debian.maven.repo.Repository.r= egisterPom(Repository.java:419)<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 at<br>org.de= bian.maven.packager.DependenciesSolver.resolveDependencies(DependenciesSolv= er.java:320)<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 at<br>org.debian.maven.packager= .DependenciesSolver.resolveDependencies(DependenciesSolver.java:420)<br>=C2= =A0 =C2=A0 =C2=A0 =C2=A0 at<br>org.debian.maven.packager.DependenciesSolver= .solveDependencies(DependenciesSolver.java:260)<br>=C2=A0 =C2=A0 =C2=A0 =C2= =A0 at<br>org.debian.maven.packager.DependenciesSolver.main(DependenciesSol= ver.java:922)<br>```<br><br>The way it is set up is that all subprojects us= e the `${revision}` placeholder<br>to resolve the parent POM's version.= I believe this was introduced in maven 3.5.<br>The project builds normally= when `mvn package` is invoked.<br><br>=C2=A0 =C2=A0* What was the outcome = of this action?<br>=C2=A0 =C2=A0`mh_make` crashed<br><br>=C2=A0 =C2=A0* Wha= t outcome did you expect instead?<br>=C2=A0 =C2=A0`mh_make` to resolve the = dependency with the parent pom and continue with<br>the setup.<br><br><br>-= - System Information:<br>Debian Release: bookworm/sid<br>=C2=A0 APT prefers= jammy-updates<br>=C2=A0 APT policy: (500, 'jammy-updates'), (500, = 'jammy-security'), (500, 'jammy'), (100, 'jammy-backpor= ts')<br>Architecture: amd64 (x86_64)<br>Foreign Architectures: i386<br>= <br>Kernel: Linux 6.2.6-76060206-generic (SMP w/8 CPU threads; PREEMPT)<br>= Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE<br>Locale: LANG= =3Den_US.UTF-8, LC_CTYPE=3Den_US.UTF-8 (charmap=3DUTF-8), LANGUAGE not set<= br>Shell: /bin/sh linked to /usr/bin/dash<br>Init: systemd (via /run/system= d/system)<br>LSM: AppArmor: enabled<br><br>Versions of packages maven-debia= n-helper depends on:<br>ii =C2=A0default-jdk =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 2:1.11-72build2<br>ii =C2=A0defau= lt-jdk-headless =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A02:1.11-72build2<br= >ii =C2=A0libmaven-clean-plugin-java =C2=A0 =C2=A0 =C2=A03.1.0-1<br>ii =C2= =A0libmaven-compiler-plugin-java =C2=A0 3.8.1-4<br>ii =C2=A0libmaven-jar-pl= ugin-java =C2=A0 =C2=A0 =C2=A0 =C2=A03.1.2-1<br>ii =C2=A0libmaven-resources= -plugin-java =C2=A03.1.0-1<br>ii =C2=A0libmaven-site-plugin-java =C2=A0 =C2= =A0 =C2=A0 3.6-4<br>ii =C2=A0libplexus-velocity-java =C2=A0 =C2=A0 =C2=A0 = =C2=A0 1.2-3.1<br>ii =C2=A0libsurefire-java =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A02.22.3-1<br>ii =C2=A0libxml2-utils =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 2.9.13+dfsg-1ubuntu0.3<br>= ii =C2=A0maven =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 3.6.3-5<br>ii =C2=A0maven-repo-helper =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 1.10<br>ii =C2=A0unzip =C2=A0= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 6.0-26ubuntu3.1<br>ii =C2=A0velocity =C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A01.7-6<br><br>maven-= debian-helper recommends no packages.<br><br>Versions of packages maven-deb= ian-helper suggests:<br>ii =C2=A0apt-file =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A03.2.2<br>ii =C2=A0libmaven-jav= adoc-plugin-java =C2=A03.0.1-4<br>ii =C2=A0licensecheck =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A03.2.14-2<br>pn =C2=A0subversio= n =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<= none><br><br>-- no debconf information<br></div> --000000000000dac93105fb585678-- ]