Comments (2)
Thinking around loading jruby-complete.jar
...
In order to have this JAR available within the main Gradle runner, we have two options I believe
[1] Specify require version in buildscript
buildscript {
dependencies {
classpath 'org.jruby.jruby-complete:1.7.15'
}
}
Relatively simple, but causes a conflict in UX. There is already a jruby.jrubyVersion
and a `jruby.execVersion' that respectively controls the version for artifact building and executing ruby scripts. Now we are adding a 3rd way? Maybe not such a good idea
[2] Use a classloader. This is more complex to code, but is could actually utilise the jruby.jrubyVersion
value and late-load the jar. However, we need to be sure that we only ever load one version of jruby-complete
within the Gradle process. We also need to be sure as to when we are going to need this within the process. What if we start using ruby scripting as part of configuration? Since jruby.jrubyVersion
is not fully set until project.evaluate()
is called, we could end up in the nasty situation where we need to load a version of jruby only to be told later that it is the wrong version. Now option 1 suddenly looks better...
from jruby-gradle-plugin.
We have JRubyExec
now and I've not seen other needs for embedding Ruby in Gradle files so I'm going to close this
from jruby-gradle-plugin.
Related Issues (20)
- Gradle 7.1 deprecation warnings
- Custom gem repository not working with jruby-gradle-plugin 2.0.1 (plain command line gem does work with the same custom repo in .gemrc) HOT 5
- Requesting non-alpha 2.1.0 release HOT 7
- JRubyPrepare projectOperations missing input or output annotation HOT 1
- JRubyPrepare task fails on Windows Github Actions
- Gradle 7 deprecation warnings HOT 1
- Cannot install Nokogiri 1.14.0 HOT 1
- Test multiple gradle versions using https://github.com/gradle/gradle-build-action
- Remove traces of bintray publishing
- Move packages to dedicated "jruby-gradle" account in plugins.gradle.org HOT 1
- Java 8 support
- Publishing GitHub Pages
- `JRubyExec` doesn't stop on debugger
- 'jruby-gradle-core-plugin` Second Level Dependency Moved/Removed From Maven Central and Gradle Plugin Portal HOT 3
- example run-simple-ruby-script gradlew run error
- `setMain` in `JRubyExec` is removed in Gradle 8 and hence the plugin doesn't work
- `Cannot fingerprint input property 'gemConfiguration'`
- Gradle 8 compatibility?
- JRuby Gradle plugin does not resolve anymore HOT 1
- Base plugin does not work with Gradle 8.8
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from jruby-gradle-plugin.