Manage jar dependencies similar to how bundler manages gem dependencies:
- the DSL mimics the one from bundler
- you can use maven-like version declarations or rubygems/bundler version ranges
- it locks down the jar versions inside "Jarfile.lock"
- you can declare jar dependencies within a gem using the requirements directive of the gem specification. jbundler will include those jar dependencies into its classpath
differences compared to bundler
- you need to run
bundle installfirst if any of the gems have jar dependencies.
- all one command
jbundle helpon the possible options and how to update a single jar, etc.
Install JBundler with:
jruby -S gem install jbundler
First, create a Jarfile, something like:
jar 'org.yaml:snakeyaml', '1.14' jar 'org.slf4j:slf4j-simple', '>1.1'
Install jar dependencies
jruby -S jbundle install
Loading the jar files
It will add all the jar dependencies in the java classpath from the
For adding a maven repository see Jarfile.
Building the jbundler gem
Running the integration test
Building the gem (see ./pkg)
./mvnw package -Dinvoker.skip
gem build jbundler.gemspec
src/example/my_project has a Gemfile which uses a gem which depends on jar dependency. See src/example/gem_with_jar/gem_with_jar.gemspec how the jar gets declared.
Execute src/example/my_project/info.rb to see it in action:
cd src/example/my_project jbundle install bundle exec info.rb
Since the version resolution happens in two steps - first the gems, and then the jars/poms - it is possible in case of a failure that there is a valid gems/jars version resolution which satisfies all version contraints. So there is plenty of space for improvements (like maven could resolve the gems as well, etc).
The whole project actually started with a controversial discussion on a pull request on bundler. This very same pull request were the starting point of that project here. Probably by now there is not much left of the original code, but many thanks to ANithian for giving the seed of that project.
Almost all code is under the MIT license but the java class (AetherSettings.java)[https://github.com/mkristian/jbundler/blob/master/src/main/java/jbundler/AetherSettings.java] which was derived from EPL licensed code.
- Fork it
- Create your feature branch (
git checkout -b my-new-feature)
- Commit your changes (
git commit -am 'Added some feature')
- Push to the branch (
git push origin my-new-feature)
- Create new Pull Request