Most extensions on https://quarkus.io/extensions have enriched information (icon, issue counts, etc) which we pull from GitHub. The starting point is SCM coordinates in the extension metadata file. That information gets into the file by a few mechanisms: if the extension is built on GitHub using the extension is built using GitHub Actions we pull the information from environment variables, or else we can also read it from the pom.xml. It would be great if the Vaadin extension also has this information available.
I haven't done a PR since I'm not sure which mechanism you'd prefer:
Set the environment variable GITHUB_REPOSITORY to vaadin\quarkus in the build
Add this to thepom.xmls (definitely runtime pom, and the others wouldn't hurt):
Most extensions on https://quarkus.io/extensions have enriched information (icon, issue counts, etc) which we pull from GitHub. The starting point is SCM coordinates in the extension metadata file. That information gets into the file by a few mechanisms: if the extension is built on GitHub using the extension is built using GitHub Actions we pull the information from environment variables, or else we can also read it from the pom.xml. It would be great if the Vaadin extension also has this information available.
I haven't done a PR since I'm not sure which mechanism you'd prefer:
Set the environment variable
GITHUB_REPOSITORY
tovaadin\quarkus
in the buildAdd this to the
pom.xml
s (definitely runtime pom, and the others wouldn't hurt):To check it's working, you can have a peek in the generated
quarkus-extension.yml
in the runtime project to make sure there's an scm field.