These are chat archives for jruby-gradle/jruby-gradle-plugin
JRuby Gradle: GitHub: https://github.com/jruby-gradle || Bintray: https://bintray.com/jruby-gradle || Mailing list: https://groups.google.com/forum/#!forum/jruby-gradle
gemWorkDirissue. I have been thinking. Removing the
@OutputDirectoryis not the correct solution, neither is leaving it there the correct solution atm as well.
spectask to be run whenever you need it to, but you maybe have to figure out what it means for the spec task to be up to date.
@InputDirectory. If it is something that is part of you specific build script then it is done via
specis dependent on say files in your
testsdirectory you can do
inputs.dir file(‘tests’)in the configuration closure for the task.
specafter absolutely nothing has changed, you run
I was thinking about building a "batteries included" plugin that includes the spec task, and some other common tasks
Try it out - tell people it’s incubating. It can serve as a good learning platform to figure out how to move the jruby integration forward. As I’ve said before - I would like to see if it is possible to build a complete Ruby project in grade (without having to resort to rake on the command-line).