Re: Next question for help in Java packaging: beast-mcmc

2011-03-13 Thread Giovanni Mascellani
Hi. On 13/03/2011 16:03, Eric Lavarde wrote: > The reality is that, invoked with -jar, java ignores any classpath from > the command line and uses only the one from the manifest, which explains > the differences in behavior your are experiencing. I considered this option, which partially solves t

Re: Next question for help in Java packaging: beast-mcmc

2011-03-13 Thread Eric Lavarde
Hi, On 12/03/11 12:13, Giovanni Mascellani wrote: Third try: if I explicitly set classpath with this line java -cp /usr/share/beast-mcmc/lib/beast.jar:/usr/share/java/jam.jar:/usr/share/java/jdom1.jar:/usr/share/java/jebl.jar:/usr/share/java/commons-math.jar dr.app.beast.BeastMain then the pro

Re: Next question for help in Java packaging: beast-mcmc

2011-03-12 Thread Giovanni Mascellani
Hi Andreas. On 28/02/2011 22:51, Andreas Tille wrote: > Hi, > > I would like to refresh my question about the problem I mentioned. > Here again a short summary: At > >http://people.debian.org/~tille/packages/beast-mcmc-help-wanted/ > > you can find a source package of beast-mcmc. All prec

Re: Next question for help in Java packaging: beast-mcmc

2011-02-28 Thread Andreas Tille
Hi, I would like to refresh my question about the problem I mentioned. Here again a short summary: At http://people.debian.org/~tille/packages/beast-mcmc-help-wanted/ you can find a source package of beast-mcmc. All preconditions which are not available in Debian are at http://people.de

Re: Next question for help in Java packaging: beast-mcmc

2011-02-18 Thread Andreas Tille
On Fri, Feb 18, 2011 at 04:37:53PM +0100, Vincent Fourmond wrote: > > This could mean that the version of jam in NEW was built without > support for one of its components (this can happen sometimes with > complex ant files), or that these components were split somehow. Where > can I get the pack

Re: Next question for help in Java packaging: beast-mcmc

2011-02-18 Thread Vincent Fourmond
On Wed, Feb 16, 2011 at 10:59 PM, Andreas Tille wrote: > when dealing with phylogenie related programs I found several Java based > programs up for packaging.  I've got FigTree close to ready - just one > JAR (iText PDF library) is up for isolation of binary JAR into separate > package (will be to

Re: Next question for help in Java packaging: beast-mcmc

2011-02-18 Thread Andreas Tille
On Fri, Feb 18, 2011 at 09:31:09AM -0500, Scott Howard wrote: > > ... but failed.  Any idea why this does not work? > > Is it failing when you try to execute the .jar? (Saying can't find jam.jar?) Yes. > I don't know the insides of jh_manifest and dh7 style commands, but I > usually see debian/

Re: Next question for help in Java packaging: beast-mcmc

2011-02-18 Thread Andreas Tille
On Fri, Feb 18, 2011 at 02:06:54PM +0100, Niels Thykier wrote: > > jh_manifest follows the symlink and updates the original jar file rather > than creating a copy of the original jar file and updating that copy. > > That being said; java generally does not support multiple purpose jars > via the

Re: Next question for help in Java packaging: beast-mcmc

2011-02-18 Thread Andreas Tille
> >   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

Re: Next question for help in Java packaging: beast-mcmc

2011-02-17 Thread Scott Howard
On Thu, Feb 17, 2011 at 3:49 AM, Andreas Tille wrote: > The problem I had is that beast-mcmc contains more than one executables > with more than one JAR files.  Some executables are using a common JAR > file with different main classes.  As far as I have seen this case > is not covered by the tuto

Re: Next question for help in Java packaging: beast-mcmc

2011-02-17 Thread Andreas Tille
On Wed, Feb 16, 2011 at 06:12:53PM -0500, Scott Howard wrote: > I haven't built the package, but the debian/__beast-mcmc.manifest__ > doesn't appear to be in javahelper manifest form. No it is definitely not - it was just a reminder for myself what classes need to be called. The __*__ made sure t

Re: Next question for help in Java packaging: beast-mcmc

2011-02-16 Thread Scott Howard
On Wed, Feb 16, 2011 at 4:59 PM, Andreas Tille wrote: > with debian/figtree.manifest which was determining the CLASSPATH for the > executable jar.  I considered this way as quite useful and would like to > try it for beast-mcmc as well (even if it is no real request - any other > way would be welc

Next question for help in Java packaging: beast-mcmc

2011-02-16 Thread Andreas Tille
Hi, when dealing with phylogenie related programs I found several Java based programs up for packaging. I've got FigTree close to ready - just one JAR (iText PDF library) is up for isolation of binary JAR into separate package (will be topic of another mail soonish). For the package beast-mcmc[1