Currently ruby-maven is set up to copy its .mvn/extensions.xml file into the current directory when running poms from the Ruby API. This is intended to load the ruby polyglot extension, so it is always enabled and nothing more is required for ruby-maven users to user this dialect. Unfortunately due to issues discussed in https://github.com/jruby/jruby/issues/7059#issuecomment-2190953877, the current directory is not always used by Maven when looking for extensions for the current build.
We should use something more robust to ensure that Maven as run through ruby-maven always has polyglot enabled, without playing config file tricks.
Currently ruby-maven is set up to copy its
.mvn/extensions.xml
file into the current directory when running poms from the Ruby API. This is intended to load the ruby polyglot extension, so it is always enabled and nothing more is required for ruby-maven users to user this dialect. Unfortunately due to issues discussed in https://github.com/jruby/jruby/issues/7059#issuecomment-2190953877, the current directory is not always used by Maven when looking for extensions for the current build.We should use something more robust to ensure that Maven as run through ruby-maven always has polyglot enabled, without playing config file tricks.