Maven snapshot metadata not generated for versions like TRK.0-SNAPSHOT

[olivier.piron_7128]

Hi all,

I'm currently evaluating ProGet Free (Version 2026.5 Build 8) and migrating Maven repositories from Nexus using Feed Replication.

I've encountered an issue with some SNAPSHOT versions whose version string does not start with a number.

For example:

4.2.0-SNAPSHOT → works correctly
TRK.0-SNAPSHOT → problem

The package is replicated successfully:

the JAR is present and downloadable (HTTP 200),
the POM is present,
the artifact-level maven-metadata.xml is also available and contains:
TRK.0-SNAPSHOT

However, requesting the version-level snapshot metadata returns an error:

GET /maven2/erisnapshots/ch/eri/olympic-core-table-artifacts/TRK.0-SNAPSHOT/maven-metadata.xml

Response:

Metadata file was not found.

For comparison, the equivalent request for a numeric snapshot version works as expected:

GET /maven2/erisnapshots/ch/eri/olycore/4.2.0-SNAPSHOT/maven-metadata.xml

returns the expected snapshot metadata.

I have also enabled the option to allow invalid versions, but it doesn't seem to affect this behavior.

From my investigation:

the package is indexed correctly;
the version appears in the artifact-level maven-metadata.xml;
the snapshot JAR can be downloaded successfully;
only the version-level maven-metadata.xml cannot be retrieved.

Has anyone experienced this issue?

Is this a known limitation of the Maven feed, or is there a way to regenerate or expose the missing snapshot metadata for versions such as TRK.0-SNAPSHOT?

Thanks in advance for any suggestions.

[stevedennis]

Hi @olivier-piron_7128 ,

I'm afraid this behavior is somewhat expected because TRK.0 is not a valid version number.

ProGet has some limited support for invalid version numbers, but this use case falls into one of those unsupported cases.

The reason is that ProGet is "package server" (as opposed to a file server), and all of the maven-metadata.xml files are generated by ProGet, on demand, based on items in the database. Uploads of maven-metadata.xml are simply ignored.

Compare this to Nexus (a file server), which serves the client-uploaded maven-metadata.xml files, and whatever other items were uploaded to whatever directory.

TRK.0-SNAPSHOT is technically a valid artifact name but an invalid version number, so it's treated like an artifact. And, since there are no releases of that package, you get a 404.

In this case, we would suggest you to switch to using actual version numbers. My guess is that TRK.0 is some kind of work-around for something. You could instead do 9999.9.9 or something, if you needed that kind of work-around.

Hope that helps,
Steve