On 02.11.2016 05:52, Wookey wrote: > Hi chaps and chapesses, Hi Wookey,
> > I am trying to package javalution: > http://javolution.org/ > code at: > https://svn.java.net/svn/javolution~svn > > I am very vague about java in general (I don't use the language), but > have sucessfully packaged stuff which uses makefiles and ant, using > java-helper. > > However maven is new to me, and that seems to be what is in use here. > (The source has pom.xml files) > > Thre is also a load of stuff about osgi in the .pom files, which seems > to be some packaging format for java (different from jars). Do I care > about this? Can I easily just nobble the making of osgi packages and > thus simplafy my dependency tree? At the moment I'm looking at https://svn.java.net/svn/javolution~svn/tags/V6_0/javolution/core-java/pom.xml: The pom.xml looks straightforward to me. For the OSGi stuff you will have to build-depend on libosgi-core-java and libosgi-compendium-java and libmaven-bundle-plugin-java. Although it is also possible to package javolution with javahelper and a self-made ant script, I would recommend to use maven-debian-helper instead. If you run mh_make from the root directory of your package, it will generate a debian directory and then you "just" need to tweak it. For example check out jboss-xnio which makes use of maven-debian-helper. [...] > I've tried using the poms, by using mh_make to make some rules that might be > about right > (which seem to use maven via cdbs), but really don't understand what I'm > doing. > 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 > > This is listed in the pom.xml file under "Native Plugin Default Configuration > (EXE)" > with talk about 'adding support for Visual studio 2010'. I don't think I care > about > any of that, so I added > org.codehaus.mojo native-maven-plugin * * * * > to debian/maven.ignoreRules > (is that right, or is this in fact needed for building the cpp .so part?) > If it is needed how do I get it? There doesn't seem to be a packaged > maven/java > version of it. Javolution builds a Java library and a native library. If you don't need the native library your solution is correct and you can add the artifact (jar file) org.codehaus.mojo native-maven-plugin * * * * to maven.ignoreRules. Otherwise someone has to package maven-native-plugin. https://bugs.debian.org/700679 > > Next I get complaints about felix "Unresolveable build extension: Plugin > org.apache.felix:maven-bundle-plugin:2.3.7 or one of its dependencies could > not be resolved". > This seems to be some framework for osgi packaging? Does that mean I don't > need it? Just add libmaven-bundle-plugin-java to Build-Depends. I hope that will do the trick. Cheers, Markus
signature.asc
Description: OpenPGP digital signature
