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

8th
Jun 2015
R. Tyler Croy
@rtyler
Jun 08 2015 15:01
alright, I think I found a resolution bug, I'm going to try to add a gradleTest for it
@ysb33r or should things like that be done as integration tests?
rtyler @rtyler is unsure of where tests should go now
Schalk W. Cronjé
@ysb33r
Jun 08 2015 15:04
gradleTest is mostly used for compatiblity testing
R. Tyler Croy
@rtyler
Jun 08 2015 15:05
is this integration test code ever going to be turned into a plugin?
Schalk W. Cronjé
@ysb33r
Jun 08 2015 15:05
most tests that want to ‘download’ should got to integration tests
There is some integration test plugin that I need to have a look at
ysb33r @ysb33r is wondering whether these plugin can form the base of a Devoxx submission
R. Tyler Croy
@rtyler
Jun 08 2015 15:06
heh
Schalk W. Cronjé
@ysb33r
Jun 08 2015 15:06
DevoxxBE CFP is open...
R. Tyler Croy
@rtyler
Jun 08 2015 15:09
@ysb33r is there an annotation which can be used in Spock to say "this is a regression case for this issue"? or is that just something you have to comment?
Schalk W. Cronjé
@ysb33r
Jun 08 2015 15:23
@Issue
@Issue(‘http://github.com/…../isues/1313')
Also if you know the test is curretnly failing due to another issue you can add @FailsWith(ExceptionClass).
I am getting on the road now - it’s been a frustrating day. Need to clear my mind from tech for some hours.
R. Tyler Croy
@rtyler
Jun 08 2015 15:27
hope it's relaxing, catch ya later
R. Tyler Croy
@rtyler
Jun 08 2015 15:45
woot, got a reproducible issue
Christian Meier
@mkristian
Jun 08 2015 15:56
@rtyler aha - you found something new which fails
R. Tyler Croy
@rtyler
Jun 08 2015 15:58
@mkristian #130 adds a regression test :)
Christian Meier
@mkristian
Jun 08 2015 15:58
let's see if there is fix possible on plugin level
R. Tyler Croy
@rtyler
Jun 08 2015 16:01
@mkristian the version ranges aren't incompatible AFAICT
well, in the gemspecs that is
Christian Meier
@mkristian
Jun 08 2015 16:02
I am not saying that there is no combination which works. but as far I can tell gradle does not look at possible combinations to find its dependency tree
so maven can not resolve those two dependencies. let see what bundler does
R. Tyler Croy
@rtyler
Jun 08 2015 16:08
really? maven can't handle that?
it's pretty simple :P
Christian Meier
@mkristian
Jun 08 2015 16:10
well, it is first time since a very long time that I came across something which does not work on maven.
Schalk W. Cronjé
@ysb33r
Jun 08 2015 16:42
AFAIK Gradle uses an IvyResolver underneath to resolve dependencies. If you search the forum you'll also find referenceti a bug that not been fixed.
Christian Meier
@mkristian
Jun 08 2015 16:44
@rtyler so with both maven and gradle you can fix it with switching from rspec-core to rspec. bundler does work. but I also remember one case where bundler could not resolve something which maven could - but that is while ago (some version of rails with some other dependency)
R. Tyler Croy
@rtyler
Jun 08 2015 16:50
forcing the rspec version predictably works around the issue right now
Christian Meier
@mkristian
Jun 08 2015 16:51
I did not need to force rspec version ?
R. Tyler Croy
@rtyler
Jun 08 2015 16:51
you just did s/rspec-core/rspec/?
Christian Meier
@mkristian
Jun 08 2015 16:51
yes
R. Tyler Croy
@rtyler
Jun 08 2015 16:52
hrm, I started adding these dependencies individually before the new gem resolver, guess they're no longer necessary
Christian Meier
@mkristian
Jun 08 2015 16:53
@ysb33r I can not find anything related to this on the forum - not even the issue @rtyler submitted
@rtyler I personally prefer to reduce the top level deps to a minimum but not every one agrees with this ;)
R. Tyler Croy
@rtyler
Jun 08 2015 16:58
@mkristian i suppose my issue is stupid and legacy, will close won't fix it with force :)
Christian Meier
@mkristian
Jun 08 2015 16:58
not stupid. it just shows there are combinations which do not work
but I do not see a way to solve this on the plugin level. maybe because I am still missing the right API to do so or it is (what I know now) a problem with the underlying resolver of gradle.
R. Tyler Croy
@rtyler
Jun 08 2015 19:00
hrm