You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Because we're now installing gems into build/dirinfo/jrubyJar by default, this line ensures that the directory is completely cleaned every time the JRubyDirInfo object is instantiated.
This is obviously problematic. And this should be backported to v1.0.4
I think I'll remove the deleteDir from now to prevent this regression and open another enhancement request to more cleanly stage and generate the .jrubydir information when we create the jar artifact instead of the stage directory
rtyler
pushed a commit
to rtyler/jruby-gradle-plugin
that referenced
this issue
Sep 10, 2015
…directory
This will allow the dirinfo directory to be used as a staging ground but as
@mkristian correctly points out, this means the dirinfo directory will get more
and more stale/inaccurate as time goes on. This necessitates a refactored
approach to generating the .jrubydir files and injecting them into the packed
jar file
Fixesjruby-gradle#220
rtyler
pushed a commit
to rtyler/jruby-gradle-plugin
that referenced
this issue
Sep 10, 2015
…directory
This will allow the dirinfo directory to be used as a staging ground but as
@mkristian correctly points out, this means the dirinfo directory will get more
and more stale/inaccurate as time goes on. This necessitates a refactored
approach to generating the .jrubydir files and injecting them into the packed
jar file
Fixesjruby-gradle#220
Because we're now installing gems into
build/dirinfo/jrubyJar
by default, this line ensures that the directory is completely cleaned every time theJRubyDirInfo
object is instantiated.This is obviously problematic. And this should be backported to v1.0.4
Originally identified as jruby-gradle/jruby-gradle-storm-plugin#22
The text was updated successfully, but these errors were encountered: