Use nested module format for Java package names #2236
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
JRuby provides two formats for referring to java package [1]. Sequel has historically used a mix of both formats. This consolidates on the "nested module" format (Java::JavaSql::Date) vs the java style format (java.sql.Date). Apart from internal consistency, this format also presents as more idiomatic Ruby, since there are no invalid module names, such as Java::oracle.jdbc.driver.OracleDriver (
oracle
is not a valid module name).[1] https://github.com/jruby/jruby/wiki/CallingJavaFromJRuby#referencing-java-classes-using-full-qualified-class-name