can not load resources from jar anymore with jar uri #1813

Closed
mkristian opened this Issue Jul 15, 2014 · 3 comments

Projects

None yet

3 participants

@mkristian
Member

current master or jruby-1_7 branch:

build the jruby-complete jar

mvn install -Pcomplete

and then execute

bin/jruby -e 'load("jar:file://home/christian/projects/active/maven/jruby17/maven/jruby-complete/target/jruby-complete-1.7.14-SNAPSHOT.jar!/META-INF/jruby.home/bin/gem")' -- list

please adjust the absolute path - I do not know how to use relative path so.

this will produce an error like

LoadError: no such file to load -- META-INF/jruby.home/bin/gem!META-INF/jruby.home/bin/jgem
    load at org/jruby/RubyKernel.java:1081
  (root) at META-INF/jruby.home/bin/gem!META-INF/jruby.home/bin/gem:4
    load at org/jruby/RubyKernel.java:1081
  (root) at -e:1
@ratnikov
Contributor

Sounds like a bug. Will try to take a look soon.

@mkristian
Member

java -jar maven/jruby-complete/target/jruby-complete-1.7.14-SNAPSHOT.jar -e "require 'openssl'"

also fails - comes from another hint via travis.

it says

NameError: missing class or uppercase package name (`org.jruby.ext.openssl.OSSLLibrary'), caused by (NameError) cannot load Java class org.jruby.ext.openssl.OSSLLibrary
  get_proxy_or_package_under_package at org/jruby/javasupport/JavaUtilities.java:54
                      method_missing at file:/home/christian/projects/active/maven/jruby17/maven/jruby-complete/target/jruby-complete-1.7.14-SNAPSHOT.jar!/jruby/java/java_package_module_template.rb:14
                              (root) at META-INF/jruby.home/lib/ruby/shared/jopenssl/load.rb!META-INF/jruby.home/lib/ruby/shared/jopenssl/load.rb:19

the typical error when it does not find the embedded jars within jruby-complete.jar

I guess it is related but I can move it to another issue if you wish.

@mkristian
Member

actually this got fixed with the fix for #1850

@mkristian mkristian closed this Jul 23, 2014
@enebo enebo modified the milestone: JRuby 1.7.14, JRuby 1.7.15 Aug 27, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment