Switch to using central-publishing-maven-plugin.

[eamonnmcmanus]

I tested this by making a gson-parent-2.13.2 release, which however I dropped rather than publishing it. I intend to make a full release based on this change, once it is in the main branch.

There is a rather verbose incantation repeated in every module other than gson and gson-parent, to exclude those other modules from publication. There is probably a simpler way to do this, with profiles, but for now I'm going with simplicity.

Fixes #2892.

[cpovirk]

Hooray, and thank you!

[cpovirk]

I eventually concluded that we did not need this, and I've successfully released projects in that state.

But if you want to merge as-is because you know that things are working, I'm fine with that :)

[cpovirk]

I suspect that we could now remove the places where we set isInternalModule, which doesn't appear to have been used from places other than here.

But if you want to merge as-is because you know that things are working, I'm fine with that.

[eamonnmcmanus]

Yes, that's exactly right. I want to get a thing in that works and is at least moderately clean. We can tweak later.

[Marcono1234]

@eamonnmcmanus, for the release notes do you want to explicitly mention that this should fix the Eclipse and VS Code module declaration issue? (#2679)

[eamonnmcmanus]

@eamonnmcmanus, for the release notes do you want to explicitly mention that this should fix the Eclipse and VS Code module declaration issue? (#2679)

Thanks, I was trying to find that but couldn't in the moment. Do you want to suggest a wording for this note? (Or if you are able to edit them directly that would also be fine.)

[Marcono1234]

Maybe something like this (but feel free to change it as you like):

What's Changed

• Improved packaging of JPMS module declaration in Gson jar
  This fixes an issue where Eclipse and VS Code users could not refer to the Gson module name com.google.gson. See issue The module declaration is not visible in Eclipse IDE & VS Code #2679.
• ...

Markdown source:

- Improved packaging of JPMS module declaration in Gson jar\
  This fixes an issue where Eclipse and VS Code users could not refer to the Gson module name `com.google.gson`. See issue https://github.com/google/gson/issues/2679.

(I don't have permissions to edit the release notes myself.)

[eamonnmcmanus]

Maybe something like this (but feel free to change it as you like):

Thanks! Updated.

[Marcono1234]

Thanks!

I have created #2902 to try simplifying the release configuration a bit (and updating the Release Process guide). If you have time the next days or weeks please let me know what you think.
Though it is not urgent; as we saw here the current release config works fine.