jbundler 0.2.1 → 0.2.2

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    jbundler (0.2.1)
+    jbundler (0.2.2)
       ruby-maven (= 3.0.4.0.29.0)
 
 GEM

data/Readme.md

@@ -1,11 +1,13 @@
 # jbundler [![Build Status](https://secure.travis-ci.org/mkristian/jbundler.png)](http://travis-ci.org/mkristian/jbundler) #
 
+manage jar dependencies similar than **bundler** manages gem dependencies.
+
 * the DSL mimics the one from bundler
 * you can use maven like version declaration or rubygems/bundler like version ranges
-* it locks down the versions like bundler inside "Jarfile.lock"
+* it locks down the jar versions inside "Jarfile.lock"
 * you can declare jar dependency within a rubygems using the requirements directive of the gem specification. jbundler will include those jar dependencies into its classpath
 * on the first run everything get resolved, any further run just the setup of classpath is done (without any maven involved)
-* it integrates nicely with bundler when Bundler.require is used
+* it integrates nicely with bundler when Bundler.require is used (like Rails does it)
 
 ## get started
 
@@ -21,13 +23,13 @@ if you use only **rubygems** or **isolate** then following require will trigger
 
 ## example ##
 
-**please first build the jar file for the jbundler gem, see [Build.md](Build.md).** 
+**please first build the jar file for the jbundler gem, see [https://github.com/mkristian/jbundler/wiki/Build](Build).** 
 
-*example/my_project* has a Gemfile which uses a gem which depends on jar dependency. see *example/gem_with_jar/gem_with_jar.gemspec* how the jar gets declared.
+*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 *example/my_project/info.rb* to see it in action:
+execute *src/example/my_project/info.rb* to see it in action:
 
-      cd example/my_project
+      cd src/example/my_project
       jruby -S bundle install
       jruby -S bundle exec info.rb
 

metadata

@@ -2,7 +2,7 @@
 name: jbundler
 version: !ruby/object:Gem::Version 
   prerelease: 
-  version: 0.2.1
+  version: 0.2.2
 platform: ruby
 authors: 
   - Kristian Meier
@@ -54,13 +54,13 @@ description: |
 email: 
   - m.kristian@web.de
 executables: 
-  - jbundler
+  - jbundle
 extensions: []
 
 extra_rdoc_files: []
 
 files: 
-  - bin/jbundler
+  - bin/jbundle
   - lib/jbundler.rb
   - lib/jbundler.rb~
   - lib/jbundler.jar
@@ -90,7 +90,6 @@ files:
   - spec/aether_spec.rb
   - spec/setup.rb~
   - MIT-LICENSE
-  - Build.md
   - Readme.md
   - Test.md
   - Gemfile

data/Build.md

@@ -1,32 +0,0 @@
-# build jbundler #
-
-the build uses ruby-maven. **note** ruby-maven uses maven and maven is highly modular, i.e. it comes only with the core and the moment you need a plugin he first time its starts downloading it. with that in mind the first usage of (ruby-)maven involves a lot of downloading - so be prepared :)
-
-first get all the development gems in place:
-
-```jruby -S bundle install```
-
-to build the (extension) jar for the lib directory (prepare the jar before packaging the gem)
-
-```rmvn prepare-package```
-
-this also runs all the test over a couple of jruy version each in 1.8 and 1.9 mode. so these tests take some time. in skip the tests when building the gem use:
-
-```rmvn prepare-package -DskipTests```
-
-to build the gem in **target/jbundler-0.0.1.gem**
-
-```rmvn package```
-
-or once the jar file is in place then
-
-```gem build jbundler.gemspec```
-
-will do as well.
-
-## proper maven and IDEs ##
-
-once ```rmvn``` generated the **Gemfile.pom** you can use proper maven3 by setting a sybolic link from **pom.xml** to **Gemfile.pom**. in the end rmvn is just ruby wrapper around maven3. the **Gemfile.pom** is generated from the *jbundler.gemspec*, *Gemfile*, *Gemfile.lock* and *Mavenfile*.
-
-your IDE might be able to use the pom.xml to manage the project and its java sources.
-