You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 19, 2019. It is now read-only.
This loads the following plugins if they are not already loaded:
33
33
+`com.github.jrubygradle.base`
34
+
+`java`
34
35
35
36
## Using the plugin
36
37
@@ -63,47 +64,71 @@ task myJar (type :Jar) {
63
64
64
65
// All other JAR methods and properties are still valid
65
66
}
67
+
```
68
+
69
+
## Controlling the Ruby entry point script
70
+
71
+
If nothing is specified, then the bootstrap will look for a Ruby script `META-INF/init.rb`.
72
+
It is also possible to set the entry script. This must be specified relative to the root of the created JAR.
66
73
74
+
```groovy
75
+
jrubyJavaBootstrap {
76
+
jruby {
77
+
initScript = 'bin/asciidoctor'
78
+
}
79
+
}
67
80
```
68
81
82
+
It is the user's responsibility to ensure that entry point script is created and added to the JAR, be it `META-INF/init.rb`
83
+
or another specified script.
84
+
85
+
69
86
## Executable JARs
70
87
71
-
Please note that executable JARs are still an incubating feature. At this point appropriate libs will be copied
72
-
to the `META-INF/lib` directory, but a working `init.rb` is not available. It is still the responsibility of the
73
-
the user to craft an appropriate `init.rb` and copy it to `META-INF` via the provided the [metaInf {}](http://www.gradle.org/docs/current/dsl/org.gradle.api.tasks.bundling.Jar.html) closure.
74
-
75
-
```groovy
76
-
jar {
88
+
**Please note that executable JARs are still an incubating feature**.
89
+
90
+
Executable JARs are indirectly supported via the [Gradle Shadow Jar plugin](http://plugins.gradle.org/plugin/com.github.johnrengelman.shadow).
0 commit comments