When an artifact with a SNAPSHOT version is deployed in combination with properties then the Maven metadata is broken in that it swallows the SNAPSHOT. Steps to reproduce:
- Deploy a SNAPSHOT artifact.
- Get maven-metadata.xml for that artifact:
- Deploy the same SNAPSHOT artifacts using a property by adding ";property=value" to the deployment URL.
- Get maven-metadata.xml for that artifact again:
As you can see the metadata is clearly wrong because it suddenly lists a non-SNAPSHOT version that doesn't exist. This breaks Maven dependency resolution, especially when using version ranges because 0.0.1 is greater than 0.0.1-SNAPSHOT and will thus be preferred.