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

7th
Jul 2016
Schalk W. Cronjé
@ysb33r
Jul 07 2016 10:20
@rtyler I really enjoyed GradleSummit. Had a chance to tap into a lot of knowledge.
R. Tyler Croy
@rtyler
Jul 07 2016 15:56
very cool
I wish I could have made it :(
@mkristian Do you remember that issue on 'sub-java' invocations with JRuby embedded use-cases? I think I found it with the latest JRuby 9.1.2.0 and the FFI image
s/image/gem/
java not found
strange
R. Tyler Croy
@rtyler
Jul 07 2016 16:00
I think this passes locally because java is in my path
but in Jenkins it's not in the default path
Christian Meier
@mkristian
Jul 07 2016 16:01
so you are saying jruby can not fork itself when java is not in the path
R. Tyler Croy
@rtyler
Jul 07 2016 16:06
I /believe/ that is what is happening here
Christian Meier
@mkristian
Jul 07 2016 16:07
well, jruby could use ${jruby.home}/bin/java if it exists, otherwise keep the current behavior.
the error is only because ffi tries install the extension which is a noop for jruby. it would just do nothing here.
R. Tyler Croy
@rtyler
Jul 07 2016 16:08
yeah, I might fix that there as soon as I find the issue
oh you know what, ffi 1.9.10 was the last one to have a java package built
Christian Meier
@mkristian
Jul 07 2016 16:09
but I am also surprised that gradle did not pick the java platform gem of ffi - .... that is why
R. Tyler Croy
@rtyler
Jul 07 2016 16:10
well, it's resolving to the latest version, 1.9.13 which doesn't have a java gem built
Christian Meier
@mkristian
Jul 07 2016 16:10
downgrade to 1.9.10 - it is an empty gem for jruby anyways
R. Tyler Croy
@rtyler
Jul 07 2016 16:10
I did downgrade, fresh morning, fresh look found the bug faster :)
Christian Meier
@mkristian
Jul 07 2016 16:11
:)
R. Tyler Croy
@rtyler
Jul 07 2016 16:16
@mkristian did you happen to see jruby-gradle/jruby-gradle-plugin#274 this should address @wenhoujx's issues from what I was able to reproduce
if that looks fine to you, I think it's about time I cut a new release :)
Christian Meier
@mkristian
Jul 07 2016 16:18
I did see it, and looked after it you merged it :(
it resolves the issue I would think and you have added a test
go for the release
R. Tyler Croy
@rtyler
Jul 07 2016 16:23
:fire:
I think I'll call this 1.3.0
Christian Meier
@mkristian
Jul 07 2016 16:26
sound good
R. Tyler Croy
@rtyler
Jul 07 2016 16:34
I need a more powerful laptop, running these integration testsis killing me
R. Tyler Croy
@rtyler
Jul 07 2016 17:01
yey 1.3.0 is a thing
Christian Meier
@mkristian
Jul 07 2016 17:02
do you mean it is released ?
R. Tyler Croy
@rtyler
Jul 07 2016 17:05
yes
heh
Christian Meier
@mkristian
Jul 07 2016 17:06
cool
R. Tyler Croy
@rtyler
Jul 07 2016 17:06
I miss workin on this project :(
Christian Meier
@mkristian
Jul 07 2016 17:07
yep
Blane Dabney
@raelik
Jul 07 2016 18:36
@rtyler Does 1.3.0 use the latest JRuby release now?
R. Tyler Croy
@rtyler
Jul 07 2016 19:07
@raelik yes
@mkristian @headius mentioned in #jruby that this sub-process invocation might be a case of rubygems not using the full path for the java sub-process
I'll look into it later tonight after $WORK
Blane Dabney
@raelik
Jul 07 2016 20:00
Odd, I'm getting this message now when trying to use my artifact jar: Ignoring ffi-1.9.13 because its extensions are not built. Try: gem pristine ffi --version 1.9.13
Not entirely sure where that ffi dependency is coming from to be honest. This isn't a 1.3.0 problem though, I'm getting it with 1.2.x. It must be something that changed in one of my dependencies...
or it's specifically a problem with 1.9.13. Wasn't seeing this with ffi-1.9.10
Blane Dabney
@raelik
Jul 07 2016 20:07
yeah, I added a hard dependency on 1.9.10 in my build.gradle and this message went away.
Blane Dabney
@raelik
Jul 07 2016 20:13
Oh, I see why that's happening. When it installs 1.9.13 it isn't installing the -java version
There isn't one. That would be why :P
Blane Dabney
@raelik
Jul 07 2016 20:43
Well, guess I won't be going past 9.0.5.0 yet. It explodes all over my code.