Skip to content

Reenable JRuby #1229

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 0 commits into from
Closed

Reenable JRuby #1229

wants to merge 0 commits into from

Conversation

headius
Copy link
Contributor

@headius headius commented Dec 10, 2024

See #1228

@headius
Copy link
Contributor Author

headius commented Dec 10, 2024

This will need to be re-run after "jruby-head" builds get published overnight tonight or tomorrow.

@headius
Copy link
Contributor Author

headius commented Dec 10, 2024

I did not exclude Windows for now because I don't know why it wouldn't pass. If it fails again I'll look into it or exclude it again.

@headius
Copy link
Contributor Author

headius commented Dec 10, 2024

The JRuby 9.4.9.0 jobs are failing due to the version conflict. The head builds should be ok, but we may want to just remove the non-head jobs until I can figure out a workaround for the jar-dependencies conflict issue (or until JRuby 9.4.10.0 ships with a fix for it).

headius added a commit to headius/jruby that referenced this pull request Dec 10, 2024
By requiring a file from jar-dependencies here, we end up
activating whatever the default jar-dependencies gem is for the
current JRuby runtime. Later on, when the hook is running or gems
that use jars simply try to activate a newer jar-dependencies, we
get the dreaded version conflict described in
jruby/jar-dependencies#86, preventing activation of all
libraries.

The change here moves the body of the hook into the JRuby
defaults.rb for RubyGems rather than loading any files from
jar-dependencies itself. This appears to fix issues like those
seen in the jruby-9.4.9.0 builds at ruby/rdoc#1229 (bundle exec
failing to run due to the version conflict) and may fix other
reports.

This does not fix issues using a newer jar-dependencies on an
older JRuby, unfortunately.
@headius headius marked this pull request as draft December 10, 2024 22:02
@headius
Copy link
Contributor Author

headius commented Dec 10, 2024

Marked as draft until we can confirm it with patched JRuby builds.

@headius
Copy link
Contributor Author

headius commented Dec 11, 2024

Well, the jruby-head builds have started to pass, but only on macos so far. Continuing to investigate remaining issues.

@headius
Copy link
Contributor Author

headius commented Mar 4, 2025

The additional issue was actually found and fixed later: jruby/jar-dependencies#93

I tried to rebase and re-push but somehow it closed the PR. Please help!

@headius
Copy link
Contributor Author

headius commented Mar 4, 2025

Oops, I can reopen myself....

@headius headius deleted the reenable_jruby branch March 4, 2025 16:57
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.

1 participant