<div dir="ltr">Package: maven-debian-helper<br>X-Debbugs-Cc: <a href="mailto:stanislav.vdimov@gmail.com">stanislav.vdimov@gmail.com</a><br>Version: 2.6<br>Severity: normal<br><br>Dear Maintainer,<br><br>   * What led up to the situation?<br>     I tried to create a deb package for a maven project I am working on using<br>`mh_make`.<br><br>   * What exactly did you do (or not do) that was effective (or<br>     ineffective)?<br>     I invoked `mh_make` and started filling in the required information. When<br>I got to the module 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.DependenciesSolver<br>resolveDependencies<br>SEVERE: Error while resolving ./model/pom.xml: 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.DependencyNotFoundException: Dependency not found<br>com.mycompany.proj:project_name:pom:${revision}<br>        at org.debian.maven.repo.Repository.registerPom(Repository.java:419)<br>        at<br>org.debian.maven.packager.DependenciesSolver.resolveDependencies(DependenciesSolver.java:320)<br>        at<br>org.debian.maven.packager.DependenciesSolver.resolveDependencies(DependenciesSolver.java:420)<br>        at<br>org.debian.maven.packager.DependenciesSolver.solveDependencies(DependenciesSolver.java:260)<br>        at<br>org.debian.maven.packager.DependenciesSolver.main(DependenciesSolver.java:922)<br>```<br><br>The way it is set up is that all subprojects use 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>   * What was the outcome of this action?<br>   `mh_make` crashed<br><br>   * What outcome did you expect instead?<br>   `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>  APT prefers jammy-updates<br>  APT policy: (500, 'jammy-updates'), (500, 'jammy-security'), (500, 'jammy'), (100, 'jammy-backports')<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=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set<br>Shell: /bin/sh linked to /usr/bin/dash<br>Init: systemd (via /run/systemd/system)<br>LSM: AppArmor: enabled<br><br>Versions of packages maven-debian-helper depends on:<br>ii  default-jdk                     2:1.11-72build2<br>ii  default-jdk-headless            2:1.11-72build2<br>ii  libmaven-clean-plugin-java      3.1.0-1<br>ii  libmaven-compiler-plugin-java   3.8.1-4<br>ii  libmaven-jar-plugin-java        3.1.2-1<br>ii  libmaven-resources-plugin-java  3.1.0-1<br>ii  libmaven-site-plugin-java       3.6-4<br>ii  libplexus-velocity-java         1.2-3.1<br>ii  libsurefire-java                2.22.3-1<br>ii  libxml2-utils                   2.9.13+dfsg-1ubuntu0.3<br>ii  maven                           3.6.3-5<br>ii  maven-repo-helper               1.10<br>ii  unzip                           6.0-26ubuntu3.1<br>ii  velocity                        1.7-6<br><br>maven-debian-helper recommends no packages.<br><br>Versions of packages maven-debian-helper suggests:<br>ii  apt-file                      3.2.2<br>ii  libmaven-javadoc-plugin-java  3.0.1-4<br>ii  licensecheck                  3.2.14-2<br>pn  subversion                    <none><br><br>-- no debconf information<br></div>