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

19th
Apr 2015
Christian Meier
@mkristian
Apr 19 2015 03:47
@rtyler use the jars in the same way as jruby does use/load jars. avoiding problems like with nokogiri and its jars you had recently. avoiding all those twists to tell jar-dependencies or jbundler not to do certain things.
this is definitely needed for the jar plugin but IMO the exec should just use it as well, by pointing JARS_HOME to this directory with jars and not add them to the executable classpath. so might be also used by the base plugin
will look through your comments and cleanup things - thanx
R. Tyler Croy
@rtyler
Apr 19 2015 03:54
@mkristian is the goal of these changes to get the jars in a place to be included inside of the jar or inside of the classpath (e.g. for JRubyExec)?
rtyler @rtyler is learning intellij
R. Tyler Croy
@rtyler
Apr 19 2015 03:56
:/
Christian Meier
@mkristian
Apr 19 2015 06:01
jruby-gradle/jruby-gradle-jar-plugin#38 uses the "jars" inside the build directory already.
JRubyExec using them would make things more uniform.
and finally the war file . . .
R. Tyler Croy
@rtyler
Apr 19 2015 16:23
@mkristian I was more referring to #110, which as far as I can tell is what's putting the jars in the build directory
R. Tyler Croy
@rtyler
Apr 19 2015 19:53
@ysb33r from within another plugin, how might I be able to invoke shadowJar { jruby {} }? I'm aware of how this jruby{} closure gets added at runtime, but from another plugin I'm not sure how to use that code
project.tasks.findByName('shadowJar') will give me the task back, but it doesn't behave like it has the jruby closure on it