[Kde-java] Packaging an application

[KJ P]

Hello

>A simple jar distribution without a make would also be a good way. Jar +
>a readme on how to start it java -jar filename.jar would be an ok way to
>distribute binaries, as well as webstart could be thought as well.

How would you find the qtjava.jar and koala.jar files in an executable jar 
file.  They are in different libraries/paths depending on the distribution.  
These need to be included in the classpath of the of jar file as the 
following:

Manifest-Version: 1.0
Main-Class: main.class.to.execute
Class-Path: qtjava.jar koala.jar

For executable jar files I have had problems with this because they will 
then need to be placed in the directory from which the jar file runs or 
maybe a symbolic link to be set up for the inclusion of these (have not 
tried the symbolic link yet).  The only other way is to hardcode a path and 
that will not work.

These will not be picked up if you specify a classpath when executing a jar 
file.

>distribute binaries, as well as webstart could be thought as well.
Webstart also has this limitation as well.  The only differenct is is that 
it will download/install the kde jars only when they change.  Then you have 
these jars all over the place.

Please correct me if I am wrong on this and you guys get it working.  I 
would like to know as well.

Otherwise the suggestion of Richards looks the most promising so far.

Regards


Kenneth




>From: Werner Punz <werpu@gmx.at>
>Reply-To: kde-java@kde.org
>To: kde-java@kde.org
>Subject: Re: [Kde-java] Packaging an application
>Date: 01 Apr 2002 17:51:28 +0200
>
>Am Mon, 2002-04-01 um 17.43 schrieb Richard Dale:
> > On Sunday 31 March 2002 8:57 pm, George Russell wrote:
> > > How do I conviently package up a KDEJava application for end users?
> > > Any ideas?
> > kdoc is a perl application rather than C++, but it uses 'configure.in' 
>and
> > 'Makefile.in' to build and install, I adapted the same configure files 
>to
> > install kalyptus bindings utility. The gilt install could put a shell 
>script
> > with 'java <app path>/KSimpleBrowser' in the kde bin directory, which 
>would
> > start the app in the apps/share directory.
> >
> > eg /opt/kde3/bin/gilt.sh sets up a classpath including
> > /opt/kde3/apps/share/gilt/gilt.jar and calls 'java KSimpleBrowser'
> >
> > I don't know how it works - a lot of the automake/autoconf stuff seems 
>'black
> > magic' to me. But I've attached the kalyptus Makefile.in and 
>configure.in - I
> > think we need a standard install script like that for java apps, so that
> > people can just './configure ; make ; make install' as usual.
> >
> > > Does anyone want to test my Etext reader?
> > > http://dogma.freebsd-uk.eu.org/~grrussel
> > Looks pretty neat! I'm still rebuilding my system after a gcc/gcj 3.1 
>test,
> > I'll try it out as soon as I can..
> >
> > I like the line 'All below this line is obsolete' refering to the 
>previous
> > Swing version. How do you think the code compares?
> >
> > -- Richard
> >
>
>
>Mhh Richard, have you looked at jakarta ant, this would be a great tool
>to do such stuff as make, packaging etc...
>
>Also there are several java based graphical installers which could be
>used (like JEdit uses) this simplifies installing for end users
>tremendously. I think the installer route could be the way to go in the
>long term. At least this is java, once the user has a JDK1.2+ up and
>running the rest could be handled by the installer.
>A simple jar distribution without a make would also be a good way. Jar +
>a readme on how to start it java -jar filename.jar would be an ok way to
>distribute binaries, as well as webstart could be thought as well.
>
>
><< signature.asc >>




_________________________________________________________________
Join the world’s largest e-mail service with MSN Hotmail. 
http://www.hotmail.com