1. A user creates a hosted repository, and a content selector permission based on a groupId, e.g. format == "maven2" and coordinate.groupId =^ "my.test"
2. The user attempt to upload a .jar, via
3. Deployment fails:
The reason for this is that maven-metadata.xml files don't have any coordinates associated with them for the purposes of content selector evaluation. The workaround is that users can create a more complicated content selector that ORs the groupId with a path, but that's unnecessarily fiddly.
- maven-metadata.xml files have partial component coordinates assigned to them (just groupId and artifactId, I guess?) so that the scenario, above, works correctly and the client can update metadata.