jbundler 0.2.1 → 0.2.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- data/Gemfile.lock +1 -1
- data/Readme.md +8 -6
- data/bin/{jbundler → jbundle} +0 -0
- data/lib/jbundler.jar +0 -0
- metadata +3 -4
- data/Build.md +0 -32
data/Gemfile.lock
CHANGED
data/Readme.md
CHANGED
@@ -1,11 +1,13 @@
|
|
1
1
|
# jbundler [](http://travis-ci.org/mkristian/jbundler) #
|
2
2
|
|
3
|
+
manage jar dependencies similar than **bundler** manages gem dependencies.
|
4
|
+
|
3
5
|
* the DSL mimics the one from bundler
|
4
6
|
* you can use maven like version declaration or rubygems/bundler like version ranges
|
5
|
-
* it locks down the versions
|
7
|
+
* it locks down the jar versions inside "Jarfile.lock"
|
6
8
|
* 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
|
7
9
|
* on the first run everything get resolved, any further run just the setup of classpath is done (without any maven involved)
|
8
|
-
* it integrates nicely with bundler when Bundler.require is used
|
10
|
+
* it integrates nicely with bundler when Bundler.require is used (like Rails does it)
|
9
11
|
|
10
12
|
## get started
|
11
13
|
|
@@ -21,13 +23,13 @@ if you use only **rubygems** or **isolate** then following require will trigger
|
|
21
23
|
|
22
24
|
## example ##
|
23
25
|
|
24
|
-
**please first build the jar file for the jbundler gem, see [Build
|
26
|
+
**please first build the jar file for the jbundler gem, see [https://github.com/mkristian/jbundler/wiki/Build](Build).**
|
25
27
|
|
26
|
-
*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.
|
28
|
+
*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.
|
27
29
|
|
28
|
-
execute *example/my_project/info.rb* to see it in action:
|
30
|
+
execute *src/example/my_project/info.rb* to see it in action:
|
29
31
|
|
30
|
-
cd example/my_project
|
32
|
+
cd src/example/my_project
|
31
33
|
jruby -S bundle install
|
32
34
|
jruby -S bundle exec info.rb
|
33
35
|
|
data/bin/{jbundler → jbundle}
RENAMED
File without changes
|
data/lib/jbundler.jar
CHANGED
Binary file
|
metadata
CHANGED
@@ -2,7 +2,7 @@
|
|
2
2
|
name: jbundler
|
3
3
|
version: !ruby/object:Gem::Version
|
4
4
|
prerelease:
|
5
|
-
version: 0.2.
|
5
|
+
version: 0.2.2
|
6
6
|
platform: ruby
|
7
7
|
authors:
|
8
8
|
- Kristian Meier
|
@@ -54,13 +54,13 @@ description: |
|
|
54
54
|
email:
|
55
55
|
- m.kristian@web.de
|
56
56
|
executables:
|
57
|
-
-
|
57
|
+
- jbundle
|
58
58
|
extensions: []
|
59
59
|
|
60
60
|
extra_rdoc_files: []
|
61
61
|
|
62
62
|
files:
|
63
|
-
- bin/
|
63
|
+
- bin/jbundle
|
64
64
|
- lib/jbundler.rb
|
65
65
|
- lib/jbundler.rb~
|
66
66
|
- lib/jbundler.jar
|
@@ -90,7 +90,6 @@ files:
|
|
90
90
|
- spec/aether_spec.rb
|
91
91
|
- spec/setup.rb~
|
92
92
|
- MIT-LICENSE
|
93
|
-
- Build.md
|
94
93
|
- Readme.md
|
95
94
|
- Test.md
|
96
95
|
- Gemfile
|
data/Build.md
DELETED
@@ -1,32 +0,0 @@
|
|
1
|
-
# build jbundler #
|
2
|
-
|
3
|
-
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 :)
|
4
|
-
|
5
|
-
first get all the development gems in place:
|
6
|
-
|
7
|
-
```jruby -S bundle install```
|
8
|
-
|
9
|
-
to build the (extension) jar for the lib directory (prepare the jar before packaging the gem)
|
10
|
-
|
11
|
-
```rmvn prepare-package```
|
12
|
-
|
13
|
-
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:
|
14
|
-
|
15
|
-
```rmvn prepare-package -DskipTests```
|
16
|
-
|
17
|
-
to build the gem in **target/jbundler-0.0.1.gem**
|
18
|
-
|
19
|
-
```rmvn package```
|
20
|
-
|
21
|
-
or once the jar file is in place then
|
22
|
-
|
23
|
-
```gem build jbundler.gemspec```
|
24
|
-
|
25
|
-
will do as well.
|
26
|
-
|
27
|
-
## proper maven and IDEs ##
|
28
|
-
|
29
|
-
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*.
|
30
|
-
|
31
|
-
your IDE might be able to use the pom.xml to manage the project and its java sources.
|
32
|
-
|