Skip to content

Correct usage of maven-tools under JRuby 10.0.3+ and Ruby 4.0#42

Merged
headius merged 9 commits intojruby:masterfrom
chadlwilson:patch-1
Feb 4, 2026
Merged

Correct usage of maven-tools under JRuby 10.0.3+ and Ruby 4.0#42
headius merged 9 commits intojruby:masterfrom
chadlwilson:patch-1

Conversation

@chadlwilson
Copy link
Contributor

@chadlwilson chadlwilson commented Feb 4, 2026

Added bigdecimal and ostruct as runtime dependencies due to virtus EOL, and its (also EOL) transitive axiom-types requirement.

See jruby/warbler#607 for some additional info.

Also did some tidy-up

  • got CI running under modern ruby versions
  • bumped the versions of default maven plugins to latest compatible with maven 3
  • update/fixed the embedded license metadata
  • removed broken copyright-header updating logic

FWIW, I note that the sonatype fork (before migration here) at master...sonatype:maven-tools:master seems to have a dry-struct migration from virtus.

@chadlwilson chadlwilson force-pushed the patch-1 branch 2 times, most recently from 95f5b33 to f1f30c5 Compare February 4, 2026 09:34
Added bigdecimal and ostruct as runtime dependencies due to virtus EOL, and transitive dependency requirement.

See jruby/warbler#607 for additional info.
The previous versions don't work properly on modern Maven 3. Since Maven 3.9 is the only non EOL version, and Maven 3.9 is also EOL 9 months ago, this should not be a problem.

Right now users need to override these from Mavenfile to get things to work and avoid warnings, which is a pain.
ostruct is no longer a default gem; and it doesn't seem necessary when a normal struct will do
This is EOL, and broken on modern Rubies due to bad syntax, and needs replacement with something else.
@chadlwilson chadlwilson changed the title Correct usage of maven-tools under JRuby 10.0.3+ Correct usage of maven-tools under JRuby 10.0.3+ and Ruby 4.0 Feb 4, 2026
@headius
Copy link
Member

headius commented Feb 4, 2026

Good cleanup and updates! Let me know if there's more coming or if we should push an updated gem.

@headius headius merged commit 802053e into jruby:master Feb 4, 2026
9 checks passed
@chadlwilson chadlwilson deleted the patch-1 branch February 4, 2026 19:04
@chadlwilson
Copy link
Contributor Author

I think we can probably push it, already went a bit too far while trying to get this sorted and gradually untangle in my head how these bits are all related 😅

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants