|Introduction||Real Life Build Script|
|What Classes Get Included?||Links|
An open source tool for tracking Java dependencies. It builds jar files that automatically contain all the classes used directly or indirectly by the classes you explicitly include. You need this because jar.exe is not clever enough to do this on its own. GenJar runs only as an ant task. It is a complex tool controlled with an XML (extensible Markup Language) script. It will also build an extended manifest describing all the elements. Of course it has no way of knowing about dynamically loaded classes or resources. The latest version is Genjar2 1.4 Last revised/verified: 2010-11-10
Unless you plan to modify the Genjar source code, you don’t want to do this.
GenJar scans the classpath looking recursively for classes to include in the jar. These it includes in the jar. Classes in the ext directory, by default, it leaves out of the jar.
You can force it to include certain classes or tell it not to include certain classes because they will be supplied at run time in an auxiliary jar.
This build script builds Biorhythms, a signed Applet. You make genjar known to the script with: <taskdef resource=genjar.properties/> Oddly there are no properties to speak of in genjar.properties, just the name of the Java class that extends Task to implement GenJar.Here is how you would include a whole directory full of *.png resource images in your jar:
You can use the <library command to unpack and include some other library jar inside your jar. Unfortunately, the <classfilter command has no effect on just what is included with the <library command. Everything is included, needed or not! You have to set up the jar to be included on the classpath, then use the <classfilter. You can use the <class command to include just the stuff from a library needed to support a given class. You can use the <classpath command if GenJar seems to be having trouble finding some auxiliary library.
In this example we persuade GenJar to include just the classes used by the TrueZIP library jar and bundle them in
You might want to recompile GenJar to fix bugs, to figure out how it works etc. You will have to add the Ant jars to the project. GenJar.jar does not have a main-class in the manifest. Ant learns about the genjar.properties file from the taskdef statement in the ant script. It reads it and discovers the class org.apache.tools.ant.taskdefs.optional.genjar.GenJar which extends the abstract Ant Task class. Ant can dynamically load Genjar with Class.forName.asSubClass.newInstance. Ant can then call GenJar’s methods as needed.
This page is posted
Optional Replicator mirror
|no blog for this page||Canadian
Your face IP:[184.108.40.206]
You are visitor number|