Better messaging with NameErrors #1506

Merged
merged 1 commit into from Feb 26, 2014

Projects

None yet

3 participants

@jhspaybar
Contributor

provide a pass through of the java error for easier debugging when jars actually exist but a name error manifests anyways

Makes something like this https://gist.github.com/adamstegman/5077010 far easier to debug. I also ran into on my own project attempting to load jars that had a JVM Security Policy violation.

This if my first pull request, so if I did something wrong, let me know.

I consent to having my contributions licensed under EPL, GPLv2, and LGPLv2.

@jhspaybar jhspaybar provide a pass through of the java error for easier debugging when ja…
…rs actually exist but a name error manifests anyways
30eb556
@ratnikov

Sounds like you'd want that for better debugging. Perhaps do printStackTrace if runtime.getDebug() is true?

@headius
Member
headius commented Feb 26, 2014

Seems good. Well probably audit these error messages for 9k to make them all consistently useful.

@headius headius merged commit f19bc66 into jruby:jruby-1_7 Feb 26, 2014

1 check failed

default The Travis CI build could not complete due to an error
Details
@headius headius added this to the JRuby 1.7.12 milestone Feb 26, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment