I have been operating under the assumption that the extras project had no Maven Central artifacts, but that's not true! We have com.google.code.gson:gson-extras, last released in 2018. Not much has happened since, but there is at least a change to RuntimeTypeAdapterFactory to give it a recognizeSubtypes() method. The existing artifact also has a CVE logged against it, and even though that is actually not a security problem at all, it would be nicer for it not to be there.
I tried releasing a new version with the existing configuration, but it didn't work. It got as far as making a git tag and everything, but then said:
[INFO] [INFO] --- maven-deploy-plugin:3.1.3:deploy (default-deploy) @ gson-extras ---
[INFO] [INFO] Skipping artifact deployment
I'm sure there's some refinement needed to extras/pom.xml, probably similar to what's in gson/pom.xml.
We should also correct this statement in the README:
The artifacts created by this module are currently not deployed to Maven Central.
(It's technically correct, I suppose, since it says that "are currently not deployed", not that they never have been deployed.)
I have been operating under the assumption that the
extrasproject had no Maven Central artifacts, but that's not true! We havecom.google.code.gson:gson-extras, last released in 2018. Not much has happened since, but there is at least a change toRuntimeTypeAdapterFactoryto give it arecognizeSubtypes()method. The existing artifact also has a CVE logged against it, and even though that is actually not a security problem at all, it would be nicer for it not to be there.I tried releasing a new version with the existing configuration, but it didn't work. It got as far as making a git tag and everything, but then said:
I'm sure there's some refinement needed to
extras/pom.xml, probably similar to what's ingson/pom.xml.We should also correct this statement in the README:
(It's technically correct, I suppose, since it says that "are currently not deployed", not that they never have been deployed.)