Skip to content

Update snapshot deploy to use new maven infrastructure#8868

Merged
headius merged 8 commits intomasterfrom
new_maven_snapshots
Jun 14, 2025
Merged

Update snapshot deploy to use new maven infrastructure#8868
headius merged 8 commits intomasterfrom
new_maven_snapshots

Conversation

@headius
Copy link
Member

@headius headius commented Jun 12, 2025

There's a number of changes here to support deploying snapshots locally or automatically on GHA:

  • Moving GPG signing to the snapshots profile and using that profile to create snapshots instead of release.
  • Switching jruby-complete's source jar generation to use the contents of jruby-base instead of jruby-core (which was empty and now seems to be failing to generate altogether).
  • Updates to the maven configuration in the GHA jobs to use the "central" repository name.

This appears to be working to deploy snapshots now locally and on GHA, but I have some doubts:

  • Why did the jruby-complete use of jruby-core sources work before but suddenly fail. Why did it release ok for 9.4.13.0 and simply publish no sources jar (something I thought Maven Central rejected)?
  • I'm pretty sure snapshots worked fine when I started the process of updating to the latest Maven Central infrastructure last week, testing again the jruby-9.4 branch. Why then did it fail after merging those changes to master (10)?

headius added 7 commits June 11, 2025 12:58
This avoids attempting to sign the snapshots, which can't easily
be done from GHA.
Not sure why it proceeds in the release profile but this seems to
be necessary for snapshots.
jruby-complete was previously bundling jruby-core sources to
fulfull the requirement of maven central for sources to be
provided, but that artifact only published a dummy source jar. In
this snapshot work, for some reason that jruby-core source jar is
no longer created, but then jruby-complete has no sources to copy.

This change modifies jruby-complete to use jruby-base sources,
which provides the sources for JRuby itself as it should.

I am unclear on why this worked in the past, but it could be
something related to the old parent pom we no longer use. What I
have here works, but I seek a better explanation for why it broke.
@headius headius added this to the JRuby 10.0.1.0 milestone Jun 12, 2025
@headius headius force-pushed the new_maven_snapshots branch from 5c281bb to 9b6145d Compare June 12, 2025 13:42
@headius headius merged commit d976125 into master Jun 14, 2025
@headius headius deleted the new_maven_snapshots branch June 14, 2025 12:34
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