mh_make and Maven <prerequisites><maven>3.2
Hi - I've been trying to use mh_make to package a Maven project for Debian.
To start light-weight I have begun with just the Maven Parent pom of
our project.
https://github.com/stain/incubator-taverna-maven-parent/tree/debian
after some struggles with the plugins mh_make generated me a nice set
of debian/ files:
https://github.com/stain/incubator-taverna-maven-parent/tree/debian/debian
However, I get this error message in Debian unstable when I try to do:
dpkg-buildpackage -b
cd . && /usr/lib/jvm/default-java/bin/java -noverify -cp
/usr/share/maven2/boot/classworlds.jar:/usr/lib/jvm/default-java/lib/tools.jar
-Dproperties.file.manual=/root/src/incubator-taverna-maven-parent/debian/maven.properties
-Dclassworlds.conf=/etc/maven2/m2-debian.conf
org.codehaus.classworlds.Launcher -s/etc/maven2/settings-debian.xml
-Dmaven.repo.local=/root/src/incubator-taverna-maven-parent/debian/maven-repo
clean
[INFO]
NOTE: Maven is executing in offline mode. Any artifacts not already in
your local
repository will be inaccessible.
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Unable to build project
'/root/src/incubator-taverna-maven-parent/pom.xml; it requires Maven
version 3.2.0
This is caused by our pom.xml
<prerequisites>
<maven>3.2.0</maven>
</prerequisites>
and mvn-debian being a decade out of date:
root@25d478a1c2a6:~/src/incubator-taverna-maven-parent# mvn-debian -v
Apache Maven 2.2.1 (rdebian-16)
Is there a plan to update mvn-debian or a way to change my debian/
files to use Maven 3.x?
Is there a debian/maven* rule I can add to edit/remove the
<prerequisites> element at build time?
Manually deleting <prerequisites> element seems to work for the parent
pom - but I suspect Maven 2.2 will struggle with the rest of our
source code. I don't want to suggest Maven 2.x for non-Debian users of
our code as that would be quite fragile.
We might have been overly cautious in specifying 3.2.0 - it might work
fine with 3.0, but we have not been testing with such older versions
of Maven.
--
Stian Soiland-Reyes
Apache Taverna (incubating)
http://orcid.org/0000-0001-9842-9718
Reply to: