-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I should be able to override jruby.defaultVersion or execVersion from the command line #131
Comments
+1
|
I don't think the plugin should provide that functionality. It is better that is provided in a bespoke manner in the build script, should the author prefer it as such. |
Having said that, it would be better to do it via a system property, rather than the project property. There is some semantic invovled here. In this way if is effectivley a property of the plugin rather than the specific project. |
actually I was reading it as probably since I not aware what -P is meant for |
@ysb33r I'm fine with a system property, I can kind of understand why you don't think the functionality that the code should go into the plugin. I think there is immense benefit to JRuby users and the JRuby core team by enabling this functionality across the board by default for jruby-gradle users. That would make it absolutely trivial for jruby-gradle projects to contribute feedback to the project on the success of jruby 9k which is pretty important IMO |
I am with you on that. It will also allow to set up an additional travis axis to compile with the normal & 9K I think you just need to do something like String defaultVersion = System.getProperty('jruby.defaultVersion') ?: '1.7.20'
String execVersion = System.getProperty('jruby.execVersion') ?: defaultVersion |
👍 I'll submit a PR later today |
I'm back to thinking this should be a project property which affords the user the greatest amount of flexibility (IMHO) since they can take advantage of the For projects at Lookout we're using |
This would be great for testing newer version of JRuby with existing builds, e.g.
From what I've read this has to be manually accounted for in the plugin and doesn't come automatically
The text was updated successfully, but these errors were encountered: