embulk 0.10.39-java → 0.10.40-java

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 301d627a0b0d489edc3c5c94e58f285caa1fabb8
-  data.tar.gz: c739b82bb0fa671431855d2e61bcf4aec9d25d5f
+  metadata.gz: eb86c09a7380df5687daa279146cec893021d0a3
+  data.tar.gz: 49634221ede004b9460122e60e720ad72626d254
 SHA512:
-  metadata.gz: d3f6b01018841c2c9bc58303fb6b72113a43909f10e016e80d39b38f1b6dc92e8710d2318088dd41cef34d5df54b27034978dcddbe4c22f9e4f1a50d9dd67ee7
-  data.tar.gz: c768be23a5df9a3f057267833c3c64efd169e34f0b4460b720beaf28ff4d8b2590f06532fcdf1ff386a66fe1f7a0ac6e54a56c0a21bc27564119ee75bf5eb62f
+  metadata.gz: 7309ed9f95a0107719ffcc68b393c8bc1305ec1c849b31761441e4314c18dc0d0122015cdc303777bef69efa33a26a2172d9d0da84b6df68a8c9e6e13f80e94e
+  data.tar.gz: 6602ddcd1519a024c70570e2eca820eab8fb8579375f3eb1f78b5d51b7414541be314c132663a4bdde8e825d6ffd888a2e764e463175e96373f27f9e4da8c481

data/embulk.gemspec

@@ -1,6 +1,6 @@
 Gem::Specification.new do |gem|
   gem.name = "embulk"
-  gem.version = "0.10.39"
+  gem.version = "0.10.40"
   gem.license = "Apache-2.0"
 
   gem.summary = "Embulk's runtime library for Ruby."
@@ -33,7 +33,7 @@ Gem::Specification.new do |gem|
       "documentation_uri" => "https://www.embulk.org/",
       "homepage_uri" => gem.homepage,
       # "mailing_list_uri"  => "",
-      "source_code_uri" => "https://github.com/embulk/embulk/tree/v0.10.39",
+      "source_code_uri" => "https://github.com/embulk/embulk/tree/v0.10.40",
       # "wiki_uri" => "",
     }
   end

data/lib/embulk/error.rb

@@ -3,24 +3,98 @@ module Embulk
   # ConfigError is not a ::StandardError but is a java.lang.RuntimeException.
   # "rescue => e" can rescues ConfigError.
   class ConfigError < Java::Config::ConfigException
-    def initialize(message=nil)
-      if message
-        super(message.to_s)
-      else
-        super()
-      end
+    # :call-seq:
+    #   ConfigError.new()
+    #   ConfigError.new(string)
+    #
+    # Returns the new +ConfigError+ object.
+    #
+    # The signature of +ConfigError.new+ accepts any argument. But in fact, it
+    # accepts only <tt>ConfigError.new()</tt> and <tt>ConfigError.new(String)</tt>.
+    # It raises <tt>Error: org.jruby.exceptions.Argument</tt> otherwise. It has
+    # been like this since \Embulk v0.10.38 because a subclass of a Java class is
+    # a full Java class as of JRuby 9.3, which introduced some restrictions.
+    #
+    # See also:
+    # - https://github.com/jruby/jruby/wiki/CallingJavaFromJRuby#subclassing-a-java-class
+    # - https://github.com/jruby/jruby/issues/7221
+    #
+    # ==== History
+    #
+    # +ConfigError.initialize+ receives only a variable-length argument list
+    # (rest parameters) since \Embulk v0.10.38. It is to satisfy restrictions
+    # as of JRuby 9.3.
+    #
+    # It was <tt>ConfigError.initialize(message=nil)</tt> before v0.10.38.
+    # It switched over to call <tt>super()</tt> (<tt>ConfigException()</tt>),
+    # or <tt>super(String)</tt> (<tt>ConfigException(String)</tt>) based on
+    # +message+. It was because Ruby does not allow method overloading, and
+    # then, +ConfigError+ can have only a single +initialize+ method.
+    #
+    # On the other hand, JRuby 9.3+ does not allow +initialize+ to contain
+    # multiple +super+ calls in it. Switching the superclass constructor is
+    # no longer accepted in JRuby 9.3+.
+    #
+    # To keep compatibility from caller's viewpoint, +ConfigError.initialize+
+    # receives only a variable-length argument list (<tt>*arguments</tt>), and
+    # calls the superclass constructor with +super+ (without parenthesis). It
+    # allows <tt>ConfigError.new()</tt> and <tt>ConfigError.new(String)</tt>
+    # to call an appropriate superclass constructor for each.
+    #
+    # However, +ConfigError.new+ now accepts any argument undesirably. It
+    # raises an unexpected <tt>Error: org.jruby.exceptions.ArgumentError</tt>
+    # when +ConfigError.new+ is called with an unexpected argument.
+    def initialize(*arguments)
+      super
     end
   end
 
   # DataError is not a ::StandardError but is a java.lang.RuntimeException.
   # "rescue => e" can rescues DataError.
   class DataError < Java::SPI::DataException
-    def initialize(message=nil)
-      if message
-        super(message.to_s)
-      else
-        super()
-      end
+    # :call-seq:
+    #   DataError.new()
+    #   DataError.new(string)
+    #
+    # Returns the new +DataError+ object.
+    #
+    # The signature of +DataError.new+ accepts any argument. But in fact, it
+    # accepts only <tt>DataError.new()</tt> and <tt>DataError.new(String)</tt>.
+    # It raises <tt>Error: org.jruby.exceptions.Argument</tt> otherwise. It has
+    # been like this since \Embulk v0.10.38 because a subclass of a Java class is
+    # a full Java class as of JRuby 9.3, which introduced some restrictions.
+    #
+    # See also:
+    # - https://github.com/jruby/jruby/wiki/CallingJavaFromJRuby#subclassing-a-java-class
+    # - https://github.com/jruby/jruby/issues/7221
+    #
+    # ==== History
+    #
+    # +DataError.initialize+ receives only a variable-length argument list
+    # (rest parameters) since \Embulk v0.10.38. It is to satisfy restrictions
+    # as of JRuby 9.3.
+    #
+    # It was <tt>DataError.initialize(message=nil)</tt> before v0.10.38.
+    # It switched over to call <tt>super()</tt> (<tt>ConfigException()</tt>),
+    # or <tt>super(String)</tt> (<tt>ConfigException(String)</tt>) based on
+    # +message+. It was because Ruby does not allow method overloading, and
+    # then, +DataError+ can have only a single +initialize+ method.
+    #
+    # On the other hand, JRuby 9.3+ does not allow +initialize+ to contain
+    # multiple +super+ calls in it. Switching the superclass constructor is
+    # no longer accepted in JRuby 9.3+.
+    #
+    # To keep compatibility from caller's viewpoint, +DataError.initialize+
+    # receives only a variable-length argument list (<tt>*arguments</tt>), and
+    # calls the superclass constructor with +super+ (without parenthesis). It
+    # allows <tt>DataError.new()</tt> and <tt>DataError.new(String)</tt>
+    # to call an appropriate superclass constructor for each.
+    #
+    # However, +DataError.new+ now accepts any argument undesirably. It
+    # raises an unexpected <tt>Error: org.jruby.exceptions.ArgumentError</tt>
+    # when +DataError.new+ is called with an unexpected argument.
+    def initialize(*arguments)
+      super
     end
   end
 

data/lib/embulk/gem_version.rb

@@ -1,3 +1,3 @@
 module Embulk
-  GEM_VERSION_EMBEDDED = "0.10.39"
+  GEM_VERSION_EMBEDDED = "0.10.40"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: embulk
 version: !ruby/object:Gem::Version
-  version: 0.10.39
+  version: 0.10.40
 platform: java
 authors:
 - Sadayuki Furuhashi
@@ -10,7 +10,7 @@ authors:
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2022-12-07 00:00:00.000000000 Z
+date: 2022-12-09 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   requirement: !ruby/object:Gem::Requirement
@@ -78,7 +78,7 @@ metadata:
   changelog_uri: https://github.com/embulk/embulk/releases
   documentation_uri: https://www.embulk.org/
   homepage_uri: https://www.embulk.org/
-  source_code_uri: https://github.com/embulk/embulk/tree/v0.10.39
+  source_code_uri: https://github.com/embulk/embulk/tree/v0.10.40
 post_install_message:
 rdoc_options: []
 require_paths: