A Look at the start.jar mechanism
You're probably familiar with the handy start.jar way of running jetty:
Let's take a look at the way start.jar works and how you can customize it (if you need to).
The start.config file
The key to the mechanism is the
start.config file. This file does a number of housekeeping chores such as setting up classpaths and System properties. The default
start.config file is found in
When invoked from the command line as
-jar start.jar, the jvm looks inside the
META-INF/MANIFEST.MF file of the jar for the entry:
It then invokes the
main() method of the named class which in this instance is
org.mortbay.start.Main, which in turn parses the
start.config file and invokes the
main() method of the class named therein. It's a little clearer when we look an an #example, but first let's check out the syntax of
Each line contains an entry of the form:
- ending with ".class" is the Main class to run.
- ending with ".xml" is a configuration file for the command line
- ending with "/" is a directory from which to add all jar and zip files.
- ending with "/*" is a directory from which to add all unconsidered jar and zip files.
- ending with "/**" is a directory from which to recursively add all unconsidered jar and zip files.
- containing an "=" are used to assign system properties.
- all other subjects are treated as files to be added to the classpath.
SUBJECTmay include system properties using $(propertyname) syntax.
Files starting with "/" are considered absolute, all others are relative to the home directory.
CONDITION is one of:
- "always" (always true)
- "never" (always false)
- "available" classname (true iff classname is on the classpath)
- property name (true if property is set)
- "java" OPERATOR version (java version compared to literal)
- nargs OPERATOR number (number of command line args compared to literal)
- is one of "<",">","<=",">=","==","!="
CONTITION can be combined with "AND", "OR" or "!", with "AND" being the assumed operator for a list of
Classpath operations are evaluated on the fly, so once a class or jar is added to the classpath, subsequent available conditions will see that class.
Here's an example
start.config file that is, in fact, taken from a recent Jetty distribution.
You have two choices. You can unjar the
start.jar file and extract the
start.config file, make your changes and then re-jar it. Or, you can create your own
start.config file and then reference it on the command line like so:
If you only wish to change the class whose
main() method gets invoked after
start.config has been parsed, then you can just set the
jetty.server property instead:
Think carefully before changing the main class. The default setup ensures that any configuration files passed on the command line are parsed and Jetty is started correctly.