Self-downloading binaries, properties files #317
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
micha
force-pushed
the
download-exe
branch
4 times, most recently
from
87163df
to
0f41df8
Compare
Fixes #229 Fixes #300 Properties Files ================ - Boot now supports specifying any env var (eg. BOOT_VERSION) from properties files. - Setting BOOT_VERSION and BOOT_CLOJURE_VERSION is no longer required. - System properties are now supported in addition to properties files and environment variables. - Settings will be merged in the following order: 1. BOOT_HOME/cache/boot.properties (deprecated) 2. BOOT_HOME/boot.properties 3. <git project dir>/boot.properties 4. CWD/boot.properties 5. environment variables 6. system properties For example: CWD/boot.properties settings override BOOT_HOME/boot.properties, environment variables override all properties files, and system properties override everything else. Self-Downloading Binaries ========================= - Boot is now comprised of three pieces: the loader, application, and library. - The library is a set of Clojure dependencies in which all of the Boot namespaces are distributed. - The application is a Java uberjar that handles bootstrapping the infrastructure for creating pods and running Clojure programs. - The loader is new--it's a Java program with no dependencies that handles downloading the application as needed. It is what the user will call from the command line. - From this release onwards: - We will publish an app binary for each new boot lib version. - An exception is thrown if app and library versions don't match. - App name will be "boot.jar", cross-platform. - Loader will be "boot.sh" and "boot.exe", built in the same way as the previous versions of the app were (i.e. executable jar shell script for Unix, Launch4J executable for Windows). - Previous releases are also supported by the new loader--the loader will ensure that a compatible version of the app will be used with the specified legacy version of the boot lib. The Loader ========== - A self-contained Java program with no dependencies, packaged in executable JAR format: - Unix: JAR with bash shell script prelude (boot.sh) - Windows: Launch4J produced executable (boot.exe) - Caches app uberjar in BOOT_HOME/cache/bin/BOOT_VERSION/boot.jar. - In pseudo code this is what it does: (def app-jar-file (if BOOT_VERSION (or (cached BOOT_VERSION) (download-and-cache BOOT_VERSION)) (or (latest-cached) (download-and-cache "2.3.0")))) (defn -main [& argv] (doto (new-classloader app-jar-file) (apply-method "boot.App" "main" argv))) - There is a mapping from lib version -> app version for previous releases in the "boot/tag-release.properties" resource. This is used to download the correct version of the app for previous versions of the boot lib (when there wasn't an app release for every lib version).
micha
added a commit
that referenced
this pull request
Oct 26, 2015
Self-downloading binaries, properties files
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #229
Fixes #300
Properties Files
Boot now supports specifying any env var (eg. BOOT_VERSION) from
properties files.
Setting BOOT_VERSION and BOOT_CLOJURE_VERSION is no longer required.
System properties are now supported in addition to properties files
and environment variables.
Settings will be merged in the following order:
For example:
CWD/boot.properties settings override BOOT_HOME/boot.properties,
environment variables override all properties files, and system
properties override everything else.
Self-Downloading Binaries
library.
Boot namespaces are distributed.
infrastructure for creating pods and running Clojure programs.
handles downloading the application as needed. It is what the user
will call from the command line.
the previous versions of the app were (i.e. executable jar shell
script for Unix, Launch4J executable for Windows).
will ensure that a compatible version of the app will be used with
the specified legacy version of the boot lib.