gradle-executable-jar-plugin
gradle-executable-jar-plugin copied to clipboard
stigkj
ABANDONED - use something like the gradle-capsule-plugin instead
This is done by prepending a shell script to the resulting jar file that executes itself through java. Such a shell script could in its simplest form look like this:...
This can severly affect build time, so should be something the programmer decides on when setting up the build
Look at the library [akuma](akuma.koshuke.org) which provides Unix daemonization of Java processes.
As the application cannot be started without a main class, the build should fail if it is not set
Add a test checking that overriding which version of One-JAR to use actually works. It would look like this: ``` groovy dependencies { ... executableJar 'one-jar:one-jar-boot:0.96' ... } ```
Somehow having the Gradle Executable Jar plugin in Gradle's classpath makes tests in a module (in a multi-module project) not having the plugin applied behave differently, ie. it hangs in...
This makes it easier to support different versions of One-JAR without having to add SourceForge as a repository
When trying to load schemas (*.xsd) through SchemaFactory, like this: ``` SchemaFactory.newInstance(XMLConstants.W3C_XML_SCHEMA_NS_URI).newSchema(schemaUrl) ``` it fails with resource not found, even though the schema can be loaded from the "parent" class.