Open rtyler opened 9 years ago
One option that would address this that @mkristian and I discussed was making it such that the GemUtils. code would prune the gem specifications for versions that are not actively being used from the
$buildDir/gems` directory.
As a user, when I'm evaluating newer or older versions of a Gem, the runtime environment of
JRubyExec
may lead to inadvertently loading incorrect versions of a gem unless I explicitly./gradlew clean
between invocations of theJRubyExec
task.A concrete example, if I'm seeing issues with v2 of a gem, so I downgrade in my
build.gradle
to v1, the v2 is still inbuild/gems
and will still be used by default, whether I'm aware of it or not.This is confusing behavior and should be fixed IMO