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

ScriptingContainer.parse(PathType.CLASSPATH, "some.rb").run() fails #1869

Closed
mkristian opened this issue Jul 29, 2014 · 4 comments
Closed

ScriptingContainer.parse(PathType.CLASSPATH, "some.rb").run() fails #1869

mkristian opened this issue Jul 29, 2014 · 4 comments

Comments

@mkristian
Copy link
Member

org.jruby.embed.EvalFailedException: (TypeError) can't convert nil into String
    at org.jruby.embed.internal.EmbedEvalUnitImpl.run(EmbedEvalUnitImpl.java:133)
    at org.sonatype.nexus.ruby.DefaultRubygemsGateway.newScript(DefaultRubygemsGateway.java:48)

the code is: https://github.com/sonatype/nexus-ruby-support/blob/master/nexus-ruby-tools/src/main/java/org/sonatype/nexus/ruby/DefaultRubygemsGateway.java#L48

during the test the script lives on the currentThread.contextClassloader on production it will live inside an OSGi bundle.

works just fine with jruby-1.7.12 - jruby-1.7.13 already fails the same the current 1.7.14-SNAPSHOT

@mkristian mkristian added this to the JRuby 1.7.14 milestone Jul 29, 2014
@enebo enebo modified the milestones: JRuby 1.7.14, JRuby 1.7.15 Aug 27, 2014
@mkristian mkristian modified the milestones: JRuby 1.7.17, JRuby 1.7.15 Dec 3, 2014
@mkristian
Copy link
Member Author

not using it anymore but could be still a problem

@mkristian
Copy link
Member Author

looks related #1875

@headius
Copy link
Member

headius commented Dec 4, 2014

I fixed #1875 but I'm not sure how to test your case, since the file you linked has disappeared. If you can re-test to confirm my fix, I'd appreciate it.

@mkristian
Copy link
Member Author

unfortunately this patch alone did not fix jruby enough to run my application: so I did apply #2055 (comment) as well #2197

then fix for #1875 did fix this problem as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants