![]() Can be Maven coordinates (with optional maven:// prefix), or a file (with optional file:// prefix).īase URL for the thin.library if it is in Maven form (the default). :spring-boot-thin-launcher:1.0.29.RELEASEĪ locator for the launcher library. if thin.profile=foo the launcher searches for files called thin.properties and thin-foo.properties. The name of the properties file to search for dependency specifications and overrides.Ĭomma-separated list of profiles to use to locate thin properties. These locations plus the same paths relative /META-INF will be searched. The path to directory containing thin properties files (as per thin.name), as a comma-separated list of resource locations (directories). If you run two apps with the same parent, they will have a classpath that is the same, reading from left to right, until they actually differ. Can be used to launch a JAR file that was build with a different version of the thin launcher, for instance, or a fat jar built by Spring Boot without the thin launcher.Ī parent archive to use for dependency management and common classpath entries. If this property is defined then unresolved dependencies will be ignored when the classpath is computed, possibly leading to runtime class not found exceptions. The launcher creates a new directory here called "repository" if it doesn't exist.Īdditional classpath entries to append at runtime in the same form as you would use in java -classpath. The location of the local jar cache, laid out as a maven repository. For backwards compatibility "true" or empty are equivalent to "path". Two formats are supported: "path" and "properties". via a previous dry run) or there will be an exception.įorce dependency resolution to happen, even if dependencies have been computed, and marked as "computed" in thin.properties. All dependencies must be available locally (e.g. any value other than "false" (even empty) is true. The main class to launch (for a Spring Boot app, usually the one with resolve and download the dependencies. The thin.* properties are all removed from the command line before calling the main class, so the main class doesn't have to know how it was launched. ![]() You can set a variety of options on the command line or with system properties ( -D.). The unpack flag is false by default, so remember to set it if you want to use Maven to prepare the push. The Maven plugin has a "resolve" task with a flag unpack (or -Dthin.unpack on the command line) that creates the cache in the precise form that you need to push to Cloud Foundry. m2 to hold the local repository cache - this works because the root is the default HOME directory in a Cloud Foundry app.) $ java -jar target/demo-0.0.1.jar -thin.dryrun -thin.root=target/thin/.m2 The "app" sample in this repoĭeclares this plugin and inserts it into the "package" lifecycle: Plugin which can be used to do the dry run (download and cache theĭependencies) for the current project, or for any project that has anĮxecutable thin jar in the same format. In addition to the Spring Boot layout there is an optional Maven Variables or command line flags for its (smaller) set of optional ThinJarWrapper also accepts system properties, environment Options are removed before passing down to the Boot app. Variables ( THIN_* capitalized and underscored). ![]() ( -thin.* per Spring Boot conventions), or as environment Dthin.* can also be provided as command line arguments NOTE: options for the ThinJarLauncher that are listed as Useful trick for laying down a file system layer in a container image, Wrapper which is contained in the launcher for convenience. META-INF/thin.properties), you could run only the launcher, or the Need the application code for this (except the ![]() "thin.dryrun" (to any value except "false"). You can also do a "dry run", just to warm up the cache and not run theĪpp, by setting a System property or command line argument
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |