Re: Next question for help in Java packaging: beast-mcmc
> > jh_manifest
> > Syntax error in debian/beast-mcmc.manifest (/usr/share/beast-mcmc/beast.jar) - perhaps you are missing a ":"?
> > jh_manifest: Unknown line in debian/beast-mcmc.manifest (/usr/share/beast-mcmc/beast.jar),
>
> It looks like you're missing a : after the jar name (e.g
> /usr/share/beast-mcmc/beast.jar:)
Ahh, stupid me! Thanks for the hint.
> if you're setting both classpaths and main-classes, it's probably best
> to do it all in .manifest
I'm definitely in favour of this method and thanks to your hint I'm now
one step further.
But now it comes probably to the harder problem of having different main
classes for different functionality in the very same JAR. I updated
http://people.debian.org/~tille/packages/beast-mcmc-help-wanted/
to my latest status of packaging. My idea was to symlink
usr/share/beast-mcmc/beast.jar usr/share/beast-mcmc/loganalyser.jar
usr/share/beast-mcmc/beast.jar usr/share/beast-mcmc/logcombiner.jar
usr/share/beast-mcmc/beast.jar usr/share/beast-mcmc/treeannotator.jar
usr/share/beast-mcmc/beast.jar usr/share/beast-mcmc/treestat.jar
and use the following in the manifest:
/usr/share/beast-mcmc/loganalyser.jar:
Main-Class: dr.app.tools.LogAnalyser
Class-Path: /usr/share/beast-mcmc/beagle.jar /usr/share/java/jebl.jar /usr/share/java/jam.jar /usr/share/java/treeview.jar
/usr/share/beast-mcmc/logcombiner.jar:
Main-Class: dr.app.tools.LogCombiner
Class-Path: /usr/share/beast-mcmc/beagle.jar /usr/share/java/jebl.jar /usr/share/java/jam.jar /usr/share/java/treeview.jar
...
However, this leads to
jh_manifest
jh_manifest: Conflicting manifests for usr/share/beast-mcmc/treeannotator.jar (link) and /home/tillea/debian-maintain/repack/beast/beast-mcmc-1.6.1+svnr3660.orig/debian/beast-mcmc/usr/share/beast-mcmc/beast.jar,
so my attempt to trick manifest by samlinks does definitely not work.
Does this finally mean that the manifest method will not work in this
case? I have no idea about Java programming details but is it probably
bad style to have more than one Main-Class per JAR? Should I try to
go back to the CLASSPATH method and use the wrapper scripts provided
by upstream or should I rather talk to them to build cleaner JARs?
Kind regards
Andreas.
--
http://fam-tille.de
Reply to: