javagems 0.4.9 → 0.4.10
Sign up to get free protection for your applications and to get access to all the features.
- data/VERSION +1 -1
- data/javagems.gemspec +2 -2
- data/lib/javagems/classpath_builder.rb +3 -2
- metadata +2 -2
data/VERSION
CHANGED
@@ -1 +1 @@
|
|
1
|
-
0.4.
|
1
|
+
0.4.10
|
data/javagems.gemspec
CHANGED
@@ -5,11 +5,11 @@
|
|
5
5
|
|
6
6
|
Gem::Specification.new do |s|
|
7
7
|
s.name = %q{javagems}
|
8
|
-
s.version = "0.4.
|
8
|
+
s.version = "0.4.10"
|
9
9
|
|
10
10
|
s.required_rubygems_version = Gem::Requirement.new(">= 0") if s.respond_to? :required_rubygems_version=
|
11
11
|
s.authors = ["gabrielg", "jaknowlden"]
|
12
|
-
s.date = %q{2009-11-
|
12
|
+
s.date = %q{2009-11-20}
|
13
13
|
s.description = %q{Provides gem-esque support to Java}
|
14
14
|
s.email = %q{gabriel.gironda@gmail.com}
|
15
15
|
s.executables = ["jam", "jamc", "javagem", "javagem-exec"]
|
@@ -31,9 +31,10 @@ module JavaGems
|
|
31
31
|
Bundler.logger = real_logger
|
32
32
|
end
|
33
33
|
|
34
|
-
#
|
34
|
+
# I will find gems in a relative vendor directory and then using the system source, similar to how
|
35
|
+
# Gem Bundler will normally work
|
35
36
|
def sources
|
36
|
-
[Bundler::SystemGemSource.instance]
|
37
|
+
[Bundler::DirectorySource.new(:location => 'vendor'), Bundler::SystemGemSource.instance]
|
37
38
|
end
|
38
39
|
|
39
40
|
end # ClasspathBuilder
|
metadata
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: javagems
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 0.4.
|
4
|
+
version: 0.4.10
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- gabrielg
|
@@ -10,7 +10,7 @@ autorequire:
|
|
10
10
|
bindir: bin
|
11
11
|
cert_chain: []
|
12
12
|
|
13
|
-
date: 2009-11-
|
13
|
+
date: 2009-11-20 00:00:00 -06:00
|
14
14
|
default_executable:
|
15
15
|
dependencies:
|
16
16
|
- !ruby/object:Gem::Dependency
|