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
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.