On Thu, Jun 20, 2013 at 12:55 PM, Matthew Johnson <m...@matthew.ath.cx> wrote: > On Thu Jun 20 08:22, Eugene Zhukov wrote: >> On Thu, Jun 20, 2013 at 2:15 AM, Matthew Johnson <mj...@debian.org> wrote: >> > On Wed Jun 19 15:04, Eugene Zhukov wrote: >> >> >> Otherwise you are missing the manifest pointing to the main-class. >> >> > Yes, it works. In fact with d/foobar.links the link gets created, but >> >> > doesn't work (complains about permissions) nor jarwrapper dependency >> >> > is added. >> >> >> >> Any other ideas how to achieve this? >> > >> > I don't know how mh-make works, but yes, you have to run bits from >> > javahelper >> > to have that happen automatically. You could always just set the jar >> > executable >> > and add jarwrapper to your dependency list manually - that's all it >> > actually does. >> >> That's the point - adding jarwrapper dependency manually doesn't have >> any effect, it's completely ignored by debuild and/or >> maven-debian-helper. > > Um. How are you 'adding it manually'? If it's in the Depends: line of your > debian/control explicitly for the binary packages, nothing should be touching > that and it should be copied across verbatim...
Yes, it is copied and appears now in Depends. With foobar.links I even get the link /usr/bin/foobar -> ../share/java/foobar.jar, but it doesn't work still. > > Matt Thanks, Eugene -- To UNSUBSCRIBE, email to debian-java-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/capqgmfkhwysupjey9+husqpt1mlkbhohfczpzp8th+hkb4x...@mail.gmail.com
