Re: How should I deal with the classpath with maven-helper?

2015-09-16 21:39 GMT+02:00 Emmanuel Bourg : > Le 16/09/2015 20:13, Guillaume Turri a écrit : > >> * If I don't do anything special regarding the class-path, then I get >> the lintian warning missing-classpath [1] > > Hi Guillaume, > > You can ignore this warni

How should I deal with the classpath with maven-helper?

Hi, I'm trying to package some java code with maven-helper, and I have a few questions regarding the class-path of the built jar. To put it in a nutshell: how should it be handled? What are the good practices? More precisely: * If I don't do anything special regarding the class-path, then I get

Re: jsap in Debian?

Le 24 juil. 2015 19:30, "Emmanuel Bourg" a écrit : > You can go ahead, I confirm it isn't in Debian yet. When you are looking > for a file I suggest using apt-file, for example: > >apt-file find jsap | grep jar > > It's very useful to find the package containing a specific Maven > artifact fo

jsap in Debian?

Hi, I would like to have the Java library jsap [1] available in Debian - and I'm willing to package it if needed. When I search for it directly (apt-cache search jsap, or https://packages.debian.org/unstable/java/) I can't find it. However, when I use a search engine, I find mentions of it in re

Re: lintian: [new check] verify that JAR filename complies with Debian Java Policy

Hi, 2015-07-07 22:41 GMT+02:00 Emmanuel Bourg : > Sorry for the lack of reply, I would recommend posting your next RFS on > the debian-java list instead, you'll get more reviews here. I'll get a > look at your package. Thanks again for your first feedback on https://bugs.debian.org/cgi-bin/bugrep

Re: lintian: [new check] verify that JAR filename complies with Debian Java Policy

2015-07-07 15:26 GMT+02:00 tony mancill : > On 07/07/2015 04:15 AM, Emmanuel Bourg wrote: >> Le 06/07/2015 06:36, tony mancill a écrit : >> >>> This warning is useful because >>> some components of the Debian Java toolchain fail when JAR files don't >>> comply with the naming policy. >>> [...] > >

Re: packaging java applications: questions from a newbie

Hi, 2015-06-08 8:42 GMT+02:00 Guillaume Turri : > 2015-06-08 3:15 GMT+02:00 tony mancill : >> Hi Guillaume, >> >> I took a look at your aXMLRPC package, and it does appear to be creating >> the necessary maven artifacts and installing them into the right places, >

Re: packaging java applications: questions from a newbie

Hi, 2015-06-08 3:15 GMT+02:00 tony mancill : > Hi Guillaume, > > I took a look at your aXMLRPC package, and it does appear to be creating > the necessary maven artifacts and installing them into the right places, > so I suspect that mh_make is failing in some yet-to-be-determined manner. > > That

Re: packaging java applications: questions from a newbie

Hi, 2015-05-26 0:43 GMT+02:00 Markus Koschany : > In fact jh_build is a very simplistic way to build Java packages. It is > well suited for simple packages but I suggest to use more sophisticated > tools like maven-debian-helper for Maven projects or javahelper + > maven-repo-helper for Ant proje

Re: packaging java applications: questions from a newbie

Hi, Le 26 mai 2015 00:43, "Markus Koschany" a écrit : > [...] > Hope that helps a little > Thank you for all those pointers! I'm going to spend some time reading them and experimenting again! Regards, Guillaume -- To UNSUBSCRIBE, email to debian-java-requ...@lists.debian.org with a subject o

packaging java applications: questions from a newbie

Hi, Context === There's a Java application I've been working on during the last few years [1], and I'd like to package it. (It also uses two dependencies [2][3] which aren't available in a debian package, so I should also package them). I'm new to Debian packaging, so I've spent the last few