Issue with rake running with incorrect path about jruby-gradle-jar-plugin HOT 5 CLOSED

This looks like an issue with the $CWD from within the jar when the file is executed. I remember dealing this before but I don't remember if I actually fixed it in some other way or just decided to not use Rake as a task runner in this way.

Will have to ponder this over a beer or something

from jruby-gradle-jar-plugin.

This might not be solvable with how the execution environment from an executable .jar works. I might try to solve this with a jar-rake-runner gem or something that can be brought into the runtime environment and handles safely running Rake.application.run

from jruby-gradle-jar-plugin.

@blaines The intent to run rake as a JRubyExec was to work with items on local disk not in JARs. If you explain what your use-case is, then maybe we can suggest a solution or look at implementing some additional functionality

from jruby-gradle-jar-plugin.

@ysb33r I'm fully aware of @blaines usecase (he works on my team :)). The problem is that if you use rake as the initScript from within an executable jar it will never pick up a Rakefile located in the root of the .jar file tree.

This is much more of a bug with Rake than it is with this plugin, but I do want to find a workaround that will meet @blaines' needs

from jruby-gradle-jar-plugin.

rake now works with unexploded jar and an included Rakefile. rake still fails with rspec (and possible similar cases) - see: jruby/jruby#2969 and jruby/jruby#2968

otherwise it works now - closing

from jruby-gradle-jar-plugin.