re: Building maven packages
[I'm not on debian-java so keep me cc:ed please - I only found your
reply via the list archive]
I was hoping for some clue about this bcel versioning issue. Anyone able to shed some light?
> On Wed, 2 Nov 2016 14:21, Markus Koschany wrote:
> > On 02.11.2016 05:52, Wookey wrote:
> > > Having hacked about a bit it currenty fails with:
> > > The POM for org.codehaus.mojo:native-maven-plugin:jar:1.0-alpha-7 is missing,
> > > no dependency information available
> > Otherwise someone has to package maven-native-plugin.
> > https://bugs.debian.org/700679
> Well I don't mind doing this if it's not too hard, and I don't have too
> many more layers of java-package rabbit-hole to go :-).
> That bug says "I left the packaging work I was doing up on
> git.debian.org", but I can't find it.
> There is a 2009 https://anonscm.debian.org/cgit/users/twerner/maven-native.git
> which I think is an earlier version of the same package
> but doesn't have a debian dir, so I guess torsten didn't get very far.
> I'll mail Andres Mejia for clarification, but if anyone knows where
> existing work might be...
OK. I mailed Andres but got no response.
I've found the current version of maven-native at https://github.com/mojohaus/maven-native
and it even has a release tarball!
And I've now got a better understanding of how to use mh_make to
mostly sort things out for me.
However I've hit this issue:
------------
In native-maven-plugin/pom.xml: This dependency cannot be found in the Debian Maven repository. Ignore th\
is dependency? bcel:bcel:jar:5.1
[y/N] >
> dpkg --search /usr/share/maven-repo/bcel/bcel/*/*
dpkg failed to execute successfully
> apt-file search /usr/share/maven-repo/bcel/bcel
apt-file failed to execute successfully
> dpkg --search /usr/share/java/bcel.jar
Found libbcel-java
[error] Package libbcel-java does not contain Maven dependency bcel:bcel:jar:5.1 but there seem to be a match
If the package contains already Maven artifacts but the names don't match, try to enter a substitution rule
of the form s/groupId/newGroupId/ s/artifactId/newArtifactId/ jar s/version/newVersion/ here:
> s/bcel/bcel/ s/bcel/bcel/ jar s/5.1/5.x/
Please suggest the maintainer of package libbcel-java to add this rule to debian/maven.publishedRules
In native-maven-plugin/pom.xml: This dependency cannot be found in the Debian Maven repository. Ignore this dependency? bcel:bcel:jar:5.x
------------
dpkg -L libbcel-java has:
/usr/share/java/bcel.jar
/usr/share/maven-repo
/usr/share/maven-repo/org
/usr/share/maven-repo/org/apache
/usr/share/maven-repo/org/apache/bcel
/usr/share/maven-repo/org/apache/bcel/bcel
/usr/share/maven-repo/org/apache/bcel/bcel/5.x
/usr/share/maven-repo/org/apache/bcel/bcel/5.x/bcel-5.x.pom
/usr/share/maven-repo/org/apache/bcel/bcel/6.0
/usr/share/maven-repo/org/apache/bcel/bcel/6.0/bcel-6.0.pom
/usr/share/maven-repo/org/apache/bcel/bcel/debian
/usr/share/maven-repo/org/apache/bcel/bcel/debian/bcel-debian.pom
/usr/share/ant/lib/bcel.jar
/usr/share/java/bcel-6.0.jar
/usr/share/maven-repo/org/apache/bcel/bcel/6.0/bcel-6.0.jar
/usr/share/maven-repo/org/apache/bcel/bcel/debian/bcel-debian.jar
So why didn;t my substition rules of
s/bcel/bcel/ s/bcel/bcel/ jar s/5.1/5.x/
or
s/bcel/bcel/ s/bcel/bcel/ jar s/5.1/6.0/
work?
The upstream pom.xml has:
<dependency>
<groupId>bcel</groupId>
<artifactId>bcel</artifactId>
<version>5.1</version>
</dependency>
The only thing wrong here seems tobe the version, so what should I do
here to make mh_make happy that libjava-bcel contains the right stuff?
I also got the complaint that it can't find:
backport-util-concurrent
Do I care about that? Do I need to package that too? <sinking feeling emoji>
Also how does this 'debian' version thing work? Is that like saying
'generic/current' version? And we do that to deal with all these
packages asking for a specific version when they really don't actually
care (probably). So should I prefer to set the versions for all this
stuff to 'debian' as that's likely to stay working for longer?
Cheers for pointers.
Wookey
--
Principal hats: Linaro, Debian, Wookware, ARM
http://wookware.org/
Reply to: