These are chat archives for jruby-gradle/jruby-gradle-plugin

24th
Mar 2016
Schalk W. Cronjé
@ysb33r
Mar 24 2016 15:01
@mkristian I was looking at RubygemsServlet. I think it would be better to someone set this.cachedir to use Gradle’s gradle.startParameter.userHomeDir instead of getProperty(‘user.home’) + ‘.gradle’ as the rootdir. (still appending rubygems).
in this way caches can be redirected when -g is passed to gradle command-line
Christian Meier
@mkristian
Mar 24 2016 15:45
@ysb33r yes no problem if want to change this
Schalk W. Cronjé
@ysb33r
Mar 24 2016 15:45
when I get around to it :-}
Christian Meier
@mkristian
Mar 24 2016 15:46
:)
Schalk W. Cronjé
@ysb33r
Mar 24 2016 15:46
I’m doing an offline Gradle presentation and I’ve just stumbled over that
Christian Meier
@mkristian
Mar 24 2016 15:47
ah - I see
Schalk W. Cronjé
@ysb33r
Mar 24 2016 15:52
I’m finding all sorts of interesting little shortcomings in plygins :-}
spent nearly a day chasing obscure bugs in Gradle’s groovy & scala plugins
Christian Meier
@mkristian
Mar 24 2016 15:53
power-users have a better chance to find bugs
R. Tyler Croy
@rtyler
Mar 24 2016 18:45
heh
that's definitely @ysb33r
Schalk W. Cronjé
@ysb33r
Mar 24 2016 21:18
I’m getting this error
jrubyExec
\--- org.jruby:jruby-complete:9.0.5.0 FAILED
That is the default version of JRUby that is in version 1.2.1 of our plugins
Oh dammit, it is repository order that is messing things up in my build!!!! :fire:
Schalk W. Cronjé
@ysb33r
Mar 24 2016 22:21
I have a suspicion though that my ivypot plugin cannot download GEMs. I’m trying to think how I can debug that. I’ve use both the torquebox and lasagne.io URLs.
Schalk W. Cronjé
@ysb33r
Mar 24 2016 23:50

@mkristian This had me confused for sometime. I have the following.

repositories {
    jcenter()
    maven { url "${com.github.jrubygradle.JRubyPlugin.RUBYGEMS_RELEASE_URL}" }
}

import com.github.jrubygradle.JRubyExec
apply plugin: "com.github.jruby-gradle.base"

jruby.defaultRepositories = false

dependencies {
    gems "rubygems:colorize:0.7.7"
}

task printSomePrettyOutputPlease(type: JRubyExec) {
    description "Execute our nice local print-script.rb"
    script "${projectDir}/print-script.rb”
}

I ran it with gradle -g FOO printSomePrettyOutputPlease and then went to look for the downloaded GEMs.

To my surprise I could not find them under FOO/caches, but they appeared under build/tmp/jrubyExec/cache.
Note, I specifically tried to avoid using the servlet in this case.