Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

require_relative fails in jars #737

byteit101 opened this issue May 14, 2013 · 1 comment


None yet
2 participants
Copy link

commented May 14, 2013

Errno::ENOENT: No such file or directory - /path/to/jar/dir/classpath:jar-bootstrap.rb
      realpath at org/jruby/
       require_relative at file:/path/to/jar/dir/Demo.jar!/jruby/kernel19/kernel.rb:18
        (root) at classpath:jar-bootstrap.rb:19

Repro steps:

  1. Create jar with two files, one with contents require_relative 'other' (only tested when jar is jruby-complete)
  2. Run jar

Prebuilt detection jar: with sha1sum a2fcf685518b16a4b15b108ac20feb6e31469dac
(Build using 1.7.3 and jrubyfx's jarify command on samples/fxml/Demo.rb)
Expected behavior: jrubyfx gui popus up

enebo added a commit that referenced this issue May 15, 2013


This comment has been minimized.

Copy link

commented May 15, 2013

Fixed in commit 9a87e6e. fwiw, this special-casing used to fix this is a bit of a hack. I think ultimately we need to make a comprehensive list of tests for File.dirname and File.expand_path with classpath: paths and determine reasonable behavior. Once we do I think we can greatly simplify path processing in multiple places.

@enebo enebo closed this May 15, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.