Hi @stevedennis,
Thank you very much for your answer. From what I've read elsewhere, that's exactly what I thought.
By the way, and besides that, ProGet is a really great tool. Good job !

Regards,

Olivier

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.