by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Aug 18 09:45
    josselinchevalay commented #409
  • Aug 17 09:16
    josselinchevalay commented #409
  • Aug 06 17:09
    rtyler commented #409
  • Aug 06 14:12
    josselinchevalay reopened #409
  • Aug 06 14:12
    josselinchevalay closed #409
  • Aug 06 14:12
    josselinchevalay commented #409
  • Aug 02 20:44
    rtyler labeled #409
  • Aug 02 20:44
    rtyler labeled #409
  • Aug 02 20:44
    rtyler commented #409
  • Jul 29 12:38
    josselinchevalay opened #409
  • Jun 23 00:23
    amimas commented #404
  • Jun 22 20:31
    headius commented #408
  • Jun 22 20:26
    rtyler commented #408
  • Jun 22 20:25
    rtyler commented #408
  • Jun 22 20:13
    ysb33r commented #408
  • Jun 22 19:26
    headius opened #408
  • Jun 22 19:23
    headius commented #404
  • Jun 03 14:15
    blling opened #407
  • May 31 07:04
    boris-petrov closed #387
Blane Dabney
@raelik
The jar itself executes as the ruby interpreter
Lets me keep all my project's Ruby files on the filesystem, and I set up wrapper scripts to run jRuby, or gem binaries like irb, puma, rspec, etc
Schalk W. Cronjé
@ysb33r
@rtyler we need to sort this issue with publishing the core plugin. I think we should change it so that plugins are published to portal directly and a backup published to Bintray.
Schalk W. Cronjé
@ysb33r
ping @rtyler :point_up: I am checking up what can be done to resolve this, but I suspect no more libraries can be added to Bintray and then sync'd to Gradle portal. We might have to publish directly there and also to Bintray.
Schalk W. Cronjé
@ysb33r
Schalk W. Cronjé
@ysb33r
@rtyler have you seen gradle/plugin-portal-requests#22 ? I think you have to perform the request to add.
Oohh, I managed to do it.
Schalk W. Cronjé
@ysb33r
The world has exploded this morning with Torquebox being down again and we are only half-ready with a solution.
Boris Petrov
@boris-petrov

Hi, I'm trying to migrate to 2.0.0-alpha2 to work around Torquebox being down - I managed to get almost there but when installing the RuboCop gem, which in turn installs jaro_winkler, I get this failure:

make "DESTDIR=" clean
Makefile:225: *** multiple target patterns.  Stop.

I think for some reason the original (non-java) version of the gem is being installed and not the Java one. Any ideas why?
Another thing is that doing:

jruby.jrubyVersion = jRubyVersion

Doesn't modify the JRuby version that is used by jrubyPrepareRubocop - instead, I had to do:

tasks['jrubyPrepareRubocop'].jruby.jrubyVersion = jRubyVersion

Not sure if that is a bug or what.

Boris Petrov
@boris-petrov
Here is an example project:
https://github.com/boris-petrov/jruby-gradle-bug
Just run gradle rubocop and it doesn't work. Where am I making a mistake? This is on JDK 13.0.1, Gradle 6.0.1
Schalk W. Cronjé
@ysb33r

@boris-petrov Disclaimer. It has not been tested on JDK13, but I do not think that is the issue.
It is totally possible that the wrong GEM could have been pulled. I tested various scenarious, but there is always a chance for seomthign that behaves slightly differently.

First check that you can do is to run your build with --debug and check that the gem resolver does.

Boris Petrov
@boris-petrov
I'll do that straight away.
Actually can you try the project I shared?
It's probably going to be easier for you to debug. If it breaks as it does on my side I mean.
Schalk W. Cronjé
@ysb33r
I am doing that as well. But you might spot something before me.
Boris Petrov
@boris-petrov
Does it break for you too?
Schalk W. Cronjé
@ysb33r
You should raise a defect about the jrubyVersion you are seeing BTW
Yes it breaks.
Boris Petrov
@boris-petrov
You mean open an issue in GitHub?
Will do. Do you want me to open also for the issue with RuboCop also?
Schalk W. Cronjé
@ysb33r
It is worthwhile doing that too. At least we can add a solution to that if we figure out it is not a bug.
Also you can look in ~/.gradle/rubygems-ivyxml-cache. THat is where the Ivy cache is for the Ruby gems. It might help to with diagnosis.
Boris Petrov
@boris-petrov
I see no mention of -java when I search for jaro_winkler in the --debug output. I think this is the problem. This worked before. I'm not sure who and when decides whether to ask for the Java version of a gem but I guess the issue is somewhere there.
Corneil du Plessis
@corneil
If I had a working gradle build for generating html and pdf using :
jruby-gradle-plugin:[1.5.0,2.0) and org.asciidoctor:asciidoctorj-pdf:1.5.0-alpha.18 what should I change to get it working again?
Schalk W. Cronjé
@ysb33r
@corneil if you are using the AsciidoctorPdf tasks it should not be affected by the Torquebox issue, UNLESS you are also using the Reveal.js plugin as that directly uses the older veriosn of the jruby-gradle plugin under the hood.
@boris-petrov I agree. I am seeing the same. I don't have more time today, but I'll look into it tomorrow.
Boris Petrov
@boris-petrov
@ysb33r - thanks a lot! I appreciate your time. Is there a way to configure 1.7.0 to work without Torquebox until this is resolved?
Schalk W. Cronjé
@ysb33r
@boris-petrov Only if you have access to another maven-gem-proxy service.
Boris Petrov
@boris-petrov
Well, if there are no other public ones, then no... :D
Schalk W. Cronjé
@ysb33r
@boris-petrov You can try 2.0.0-alpha.3 (notice that the version string has been fixed to be more semver)
(once it has sync'd)
R. Tyler Croy
@rtyler
@ysb33r did you push a release?
ah, I see it
great
Boris Petrov
@boris-petrov
@ysb33r - thank you for fixing the two issues! That works like a charm now. :) However, there is a new issue with another gem:
jruby-gradle/jruby-gradle-plugin#393
Thank you for the time you invest in this!
Boris Petrov
@boris-petrov
Schalk W. Cronjé
@ysb33r
2.0.0-alpha.3 is now on GRadle plugins portal (Finally!!)
So no need to include the bintray url anymore.
@rtyler Yes, might have to push another one - but first asciidoctor-gradle now has to be updated.
Schalk W. Cronjé
@ysb33r
@boris-petrov 2.0.0-alpha.4 has been released. Just waiting for it to syn to the plugin portal.
Boris Petrov
@boris-petrov
@ysb33r - thanks a lot, I'll try it out as soon as it syncs! However, in order to be able to do all that I could with 1.7.0, this issue is also a show-stopper for me: jruby-gradle/jruby-gradle-plugin#393 I found today that there was a similar issue about an year ago that was fixed - perhaps the same issue is happening now...
R. Tyler Croy
@rtyler
@ysb33r nice work on getting that released
based on what I'm seeing on GitHub and Twitter, I'm thinking we should move forward with pushing a 2.0.0, the APIs aren't going to change IMO
Schalk W. Cronjé
@ysb33r
@rtyler It was Guillame Grossetie who stood up to help
R. Tyler Croy
@rtyler
so whatcha thinking about 2.0.0 for realsies
Schalk W. Cronjé
@ysb33r
@rtyler I reckon we bump alpha release for the rest of 2019 and then go to 2.0.0 early in Jan 2020. At the rate @boris-petrov is finding bugs, we might still have a few to fix.
Boris Petrov
@boris-petrov
haha I think I'm done with the bugs. :) With the latest alpha all seems working fine(except jruby-gradle/jruby-gradle-plugin#393 but there is a workaround for it). There is something which I've noticed but it's not consistent so I haven't opened a bug for it - sometimes the jrubyPrepare task just hangs up... CTRL+C and rerunning it fixes it most of the times. Not sure if anyone has noticed something similar.
R. Tyler Croy
@rtyler
@ysb33r what do you think is holding us back from releasing now?
Schalk W. Cronjé
@ysb33r
@rtyler Me writing the docs for core plugin. That's all. Will do it this weekend.
@boris-petrov No, I have not noticed yet. It might be worthwhile to run with --info and see and what message it hangs up.