Config file, as determined from this jar's runtime path, possibly overridden by a command-line option.
If we don't have any loggers configured, try to get at least console output setup.
If we don't have any loggers configured, try to get at least console output setup. In all likelihood the eval'd config is going to set this to something more robust, but we at least need to see errors encountered while processing the config. We also may need to rebuild this if a config file threw an exception before getting around to setting up logging.
Return the path this jar was executed from.
Return the path this jar was executed from. Depends on the presence of
a valid build.properties
file. Will return None
if it couldn't
figure out the environment.
Perform baseline command-line argument parsing.
Use information in a local
build.properties
file to determine runtime environment info like the package name, version, and installation path. This can be used to automatically load config files from aconfig/
path relative to the executable jar.An example of how to generate a
build.properties
file is included in sbt standard-project: <http://github.com/twitter/standard-project>You have to pass in an object from your package in order to identify the location of the
build.properties
file. The ClassLoader for the given object is used to load the buid.properties file, which is first searched for relative to the given class (class-package-name/build.properties), and if not found there, then it is searched for with an absolute path ("/build.properties").