Issue with plugin after new `rubyzip` release?

[ssciolla]

Hi, I'm hoping to connect with some folks working on or using the plugin to see if it's just me encountering this issue.

In the recent past, my stakeholders and I had no issue running the plugin with ArchivesSpace (AS) version v3.4.1 and v1.13 of the plugin. However, following some updates to some dependencies (in Docker images), the plugin now appears to break at least the frontend of ArchivesSpace. Our logs include the following backtrace:

Bundler::GemNotFound: Could not find rubyzip-2.3.2 in any of the sources
        materialize at /archivesspace/gems/gems/bundler-2.1.4/lib/bundler/spec_set.rb:86
               map! at org/jruby/RubyArray.java:2621
        materialize at /archivesspace/gems/gems/bundler-2.1.4/lib/bundler/spec_set.rb:80
              specs at /archivesspace/gems/gems/bundler-2.1.4/lib/bundler/definition.rb:170
          specs_for at /archivesspace/gems/gems/bundler-2.1.4/lib/bundler/definition.rb:237
    requested_specs at /archivesspace/gems/gems/bundler-2.1.4/lib/bundler/definition.rb:226
    requested_specs at /archivesspace/gems/gems/bundler-2.1.4/lib/bundler/runtime.rb:101
              setup at /archivesspace/gems/gems/bundler-2.1.4/lib/bundler/runtime.rb:20
              setup at /archivesspace/gems/gems/bundler-2.1.4/lib/bundler.rb:149
             <main> at /archivesspace/gems/gems/bundler-2.1.4/lib/bundler/setup.rb:20
         with_level at /archivesspace/gems/gems/bundler-2.1.4/lib/bundler/ui/shell.rb:136
            silence at /archivesspace/gems/gems/bundler-2.1.4/lib/bundler/ui/shell.rb:88
             <main> at /archivesspace/gems/gems/bundler-2.1.4/lib/bundler/setup.rb:20
            require at org/jruby/RubyKernel.java:974
            require at uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:158
             <main> at /archivesspace/data/tmp/jetty-0_0_0_0-8080-frontend_war-_-any-16950158768391474202/webapp/WEB-INF/config/boot.rb:10
            require at org/jruby/RubyKernel.java:974
            require at uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:83
   load_environment at uri:classloader:/jruby/rack/rails/environment3.rb:23
   load_environment at uri:classloader:/jruby/rack/rails_booter.rb:83
             <main> at <script>:1
       start_server at launcher/launcher.rb:90
               main at launcher/launcher.rb:149
             <main> at launcher/launcher.rb:242

My suspicion is that the new 2.4.1 release of rubyzip -- which is a dependency of write_xlsx, used by the plugin -- introduced this issue. At least in AS version 3.4.1, the frontend Gemfile.lock has rubyzip at 2.3.2, but the plugin now installs 2.4.1.

I've forked the plugin and attempted to pin or limit the version of rubyzip, but I think doing this introduces more issues that conflict with the backend's rubyzip version of 1.3.0 -- at least pinning to 2.3.2 and limiting to <1.4 did not work.

Thus far the only thing that has at least made the plugin load is to upgrade to AS v4.0.0-RC1 and ALSO specify the rubyzip version to <1.4 in the plugin's Gemfile. I believe this works because ArchivesSpace core is now doing the same in the frontend Gemfile.lock in version 4.

I'd love to hear whether others can reproduce this issue and, if so, what options we might have for resolving. I may very well be missing a piece of the puzzle or be misunderstanding how ArchivesSpace handles plugin gems -- though right now that seems to me the root of the problem.