On Thu Jun 20 14:39, Eugene Zhukov wrote: > >> > 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. So, you have the dependency in the binary package, you have the symlink. Is the jar executable? You must do that for binfmt_misc to even try doing anything. Your options are manually setting it to executable, or calling jh_exec after the link step, which will do it for you. Matt
Attachment:
signature.asc
Description: Digital signature