Putting Packaged Classes Into A JAR File
From: Jason Teagle (jason_at_teagster.co.uk)
Date: 10/30/03
- Next message: Brad BARCLAY: "Re: Putting Packaged Classes Into A JAR File"
- Previous message: VisionSet: "Re: Why?"
- Next in thread: Brad BARCLAY: "Re: Putting Packaged Classes Into A JAR File"
- Reply: Brad BARCLAY: "Re: Putting Packaged Classes Into A JAR File"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Thu, 30 Oct 2003 21:41:55 -0000
I've managed on a previous occasion to take a bunch of class files that were
not part of a package (OK, part of the default package for the pedantic
people out there), bundle them into a JAR file with a manifest naming the
main class, and voila - I can activate the .JAR file and the application
runs. Wonderful.
Now I'm trying to do the same with some other code, but the classes are in a
package and so are in a hierarchy. By doing this:
jar cvfm appname.jar manifest.txt *.*
from the level above the package hierarchy (which would be the place where
the class files were if there was no package) DOES put the files into the
JAR complete with their directory hierarchy (viewing the JAR confirms this).
I tried naming the main class in the manifest file both with and without the
package prefix. In neither case does the finished .JAR "execute" the
application like it did before {:v(
I looked at Sun's explanation of creating JAR files but although they
explain how to build non-packaged ones, they don't say anything about
packages.
Am I doing something wrong, or have I simply missed a step?
-- -- Jason Teagle jason@teagster.co.uk
- Next message: Brad BARCLAY: "Re: Putting Packaged Classes Into A JAR File"
- Previous message: VisionSet: "Re: Why?"
- Next in thread: Brad BARCLAY: "Re: Putting Packaged Classes Into A JAR File"
- Reply: Brad BARCLAY: "Re: Putting Packaged Classes Into A JAR File"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|