Bug#795514: maven-debian-helper: mh_make fails on module that does not exist when defined within a profile

Stephen Nelson stephen at eccostudio.com
Fri Aug 14 20:16:17 UTC 2015


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

Dear Maintainer,

I was trying to package neo4j (https://github.com/neo4j/neo4j) using mh_make. While resolving one of the poms in a module there is
reference to a non-existing module within a profile. This caused mh_make to throw the following error.

Error message:

Analysing packaging/installer-qa/pom.xml...
Cannot find pom file /home/stephen/code/neo4j/neo4j/./packaging/installer-qa/pom.xml
Aug 14, 2015 9:03:08 PM org.debian.maven.packager.DependenciesSolver resolveDependencies
SEVERE: Error while resolving ./packaging/installer-qa/pom.xml: ./packaging/installer-qa/pom.xml (No such file or directory)
Aug 14, 2015 9:03:08 PM org.debian.maven.packager.DependenciesSolver resolveDependencies
SEVERE: 
java.io.FileNotFoundException: ./packaging/installer-qa/pom.xml (No such file or directory)
	at java.io.FileInputStream.open(Native Method)
	at java.io.FileInputStream.<init>(FileInputStream.java:146)
	at org.debian.maven.util.Readers.read(Readers.java:50)
	at org.debian.maven.repo.POMReader.readPom(POMReader.java:57)
	at org.debian.maven.repo.POMTransformer.transformPom(POMTransformer.java:226)
	at org.debian.maven.packager.DependenciesSolver.getPOM(DependenciesSolver.java:500)
	at org.debian.maven.packager.DependenciesSolver.resolveDependencies(DependenciesSolver.java:296)
	at org.debian.maven.packager.DependenciesSolver.resolveDependencies(DependenciesSolver.java:421)
	at org.debian.maven.packager.DependenciesSolver.resolveDependencies(DependenciesSolver.java:421)
	at org.debian.maven.packager.DependenciesSolver.solveDependencies(DependenciesSolver.java:261)
	at org.debian.maven.packager.DependenciesSolver.main(DependenciesSolver.java:960)

I would expect mh_make to treat this as a warning and continue processing the pom.

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.1.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages maven-debian-helper depends on:
ii  default-jdk                        2:1.7-52
ii  libmaven-clean-plugin-java         2.5-1
ii  libmaven-compiler-plugin-2.5-java  2.5.1-4
ii  libmaven-jar-plugin-java           2.4-1
ii  libmaven-resources-plugin-java     2.3-8
ii  libmaven-site-plugin-java          2.1-3
ii  libplexus-velocity-java            1.1.8-1
ii  libsurefire-java                   2.17-2
ii  maven-repo-helper                  1.8.12
ii  maven2                             2.2.1-27
ii  velocity                           1.7-4

maven-debian-helper recommends no packages.

Versions of packages maven-debian-helper suggests:
ii  apt-file                      2.5.4
ii  devscripts                    2.15.8
pn  libmaven-javadoc-plugin-java  <none>
ii  subversion                    1.9.0-1

-- no debconf information



More information about the pkg-java-maintainers mailing list