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

29th
Feb 2016
Ari Maniatis
@ari
Feb 29 2016 11:26
hey everyone... I'm new here, and a little confused as to whether I need to use the maven gem proxy thing, or can fetch gems right from an old fashioned rubygems proxy (we run Nexus for that)
Christian Meier
@mkristian
Feb 29 2016 11:29
@ari the nexus 2 proxy delivers the gem artifacts just point your maven repository setup to <rubygems proxy url>/maven/releases
Ari Maniatis
@ari
Feb 29 2016 11:34
@mkristian sorry, I'm still confused. I use the dependencies {} syntax from here http://jruby-gradle.org/base/ ?
With "rubygems" as the group name always?
Christian Meier
@mkristian
Feb 29 2016 11:36
you said you have rubygems proxy on nexus. let say localhost:8081/nexus/content/repositories/gems then use localhost:8081/nexus/content/repositories/gems/maven/releases as maven repository for your gems. then gradle will pick the gems from there.
yes you still need to use the "rubygems" as group name - always !
does this make sense ?
Ari Maniatis
@ari
Feb 29 2016 11:38
Except that the nexus path looks like /content/repositories/rubygems/ So are you saying I need to create a new alias on Nexus in order for the gradle plugin to find things?
Nexus is just a simple proxy of http://rubygems.org
Christian Meier
@mkristian
Feb 29 2016 11:40
no need to do anything on nexus - just have a look at /content/repositories/rubygems/maven/releases and you will find a maven repository :)
undocumented feature :)
if you want to use this maven repo in group repo on nexus then you need to add a proxy maven repo pointing to this gem-artifact repo and add this maven proxy to your group - that is a bit annoying but the only way
Ari Maniatis
@ari
Feb 29 2016 11:42
Cool. Who knew?
Christian Meier
@mkristian
Feb 29 2016 11:43
I am the main author of the nexus ruby plugin ;) - and the maven part is used by other projects outside of nexus as well
Ari Maniatis
@ari
Feb 29 2016 11:43
So I'm assuming there is no solution with your gradle plugin for people just wanting to point to http://rubygems.org because that would require bypassing all the gradle dependency management niceness?
You need to fake a maven repo?
Christian Meier
@mkristian
Feb 29 2016 11:45
yes the maven repo format is what gradle understands. there were some attempts to do this more under the hood but did not work out. for maven there is a transport extension now which can be configured with just "https://rubugems.org" and uses it directly but with gradle this can not be done within the plugin framework of gradle - unfortunately
Ari Maniatis
@ari
Feb 29 2016 11:48
Great. That's for all your work on this. I look forward to playing with it and hopefully getting rid of bundler/warbler forever.
Christian Meier
@mkristian
Feb 29 2016 11:50
welcome - also for me, getting rid of bundler/warbler was the driving force behind this :)
Schalk W. Cronjé
@ysb33r
Feb 29 2016 11:51
\o/
yip, @mkristian has put in a bunch of smart work, since we originally started this project
Ari Maniatis
@ari
Feb 29 2016 11:57
Just a little feedback... if your docs were clearer, more people might use the project. Your 'quick start' includes a bunch of colouring text scripts that is about as far removed from real usage as ancient Egyptian history. Starting with "here is a Gemfile" and "here is build.gradle to do the same thing" is probably a better starting point.
Christian Meier
@mkristian
Feb 29 2016 11:58
that is a nice idea to for quick start
rtyler @rtyler dances
Blane Dabney
@raelik
Feb 29 2016 16:11
@ari For people just using rubygems, when you define rubygems() in your dependencies, jruby-gradle-plugin spins up a local maven proxy in-memory with the gradle process
raelik @raelik is only using rubygems repositories.
Blane Dabney
@raelik
Feb 29 2016 16:13
For a brief bit, I was using a local maven repo for one of my gems, because it was a private gem and the server we host those on requires http basic auth. But, the latest jruby-gradle-plugin support basic auth in rubygems() repository urls.