reproducible builds with gem dependencies about jruby-gradle-jar-plugin HOT 3 CLOSED

I believe that this dependency lock plugin addresses the behavior you're describing.

The problem with using a tool like bundler outside of the context of Gradle is that it would result in Gradle not being aware of the dependency tree in a meaning full way to avoid re-resolving dependencies, or associating dependencies with different configurations. It also causes many of bundlers weaknesses to affect the Gradle-based project (e.g. weak separation of groups, all gems must be present at install time, etc)

from jruby-gradle-jar-plugin.

right - I never did included such a feature with jruby-maven-plugins but via ruby-maven it works really nice to use Gemfile as DSL for maven. people found "pure" gem dependencies unusable when you have lots of gems because the dependency resoultion needs (literally) hundreds of pom.xml to do its jobs. there were reports that maven did an hour downloading on an empty local repository on such projects.

but again - some improvements here you pay with some disadvantages somewhere else. in the end one needs to pick which feels best suited ;)

from jruby-gradle-jar-plugin.

to use Gemfile as DSL for maven

I have been considering reading a Gemfile from Gradle in order to determine dependencies, but have not yet convinced myself whether it is a sensible thing to do. Currently Gradle + Torquebox does a good job of dependency resolution.

from jruby-gradle-jar-plugin.