Maven autoRefs for AsyncAPI + Avro inconsistent groupId for avro references #6711
Description
Description
Registry
Version: latest
Persistence type: in-memory
Environment
docker-compose
Steps to Reproduce
When using maven plugin with autoRefs for uploading AsyncAPI spec referencing avro files:
- this referenced avro files are registered in the same groupId as the original AsyncAPI
- any other avro file referenced by those (the ones referenced from the asyncapi.yml) are placed on different groupIds of their own
You can use this example: https://github.com/ivangsa/apicurio-registry-fork/tree/main/examples/asyncapi-avro-maven-with-references-auto
Expected vs Actual Behaviour
They should all belong the the same groupId as the original AsyncAPI (and the directly referenced avros)
Also the artifactId should be more consistent:
- either use the full qualified avro name (preffered)
- or the relative path to the parent file
Logs
