modules icon indicating copy to clipboard operation
modules copied to clipboard

Modules not updating after migration to Sonatype Central

Open bjorndarri opened this issue 6 months ago • 2 comments

Hi,

I noticed the modules of my framework have stopped updating in the list (groupId: is.codion).

The latest version in modules.properties is 0.18.34, which is the last version I published to the deprecated Sonatype OSSRH Nexus.

I migrated to the new Sonatype Central for the next version 0.18.38, which has yet to appear in the list (the missing versions 35, 36 and 37 are due to this somewhat troubled migration).

Flat Look and Feel (groupId: com.formdev) is stuck on version 3.6 (april 2025), and I know that was also migrated to Sonatype Central before publishing version 3.6.1 couple of weeks ago.

Jackson is stuck on version 2.19.0 (april 2025), 2.19.1 and 2.19.2 have been published since then, they have also migrated.

I can't explain why some modules keep updating, unless some projects are still publishing to the old OSSHR Nexus.

I had Claude Code review this theory of mine and here is its conclusion:

1. Data Source: The project relies on CSV files from the java9plusadoption S3 bucket,
    which contains results from the modulescanner tool run by Sonatype on every JAR uploaded to Maven Central.
2. The Migration Issue: When Sonatype deprecated OSSRH and introduced Sonatype Central, the modulescanner
    appears to have stopped processing new uploads to Sonatype Central. This explains why:
  - Your Codion project is stuck at 0.18.34 (last OSSRH release)
  - FlatLaf is stuck at 3.6 (also migrated to Sonatype Central)
  - Jackson is stuck at 2.19.0
3. The Workflow: The GitHub Actions workflow:
  - Downloads CSV files from the S3 bucket (aws s3 sync s3://java9plusadoption)
  - Processes them with Scanner.java to generate modules.properties
  - Since the S3 bucket isn't receiving new data from Sonatype Central uploads, newer versions aren't being detected

Could you please investigate whether the modulescanner needs to be updated to support the new platform?

bjorndarri avatar Jul 23 '25 11:07 bjorndarri

Thanks for raising this issue, @bjorndarri ... it seems like the counter stalled around the 784* mark for too long, even for Java modules. 😉

I'll ask around.

sormuras avatar Aug 01 '25 04:08 sormuras

I added this note to the top-level README.md

The job providing updates of artifacts uploaded to Maven Central is slacking since summer 2025. This comment will be removed once it starts to process correctly again.

sormuras avatar Nov 04 '25 10:11 sormuras