Update the opentelemetry.io registry with Java instrumentations

[trask]

And a strategy to keep it up-to-date would be great.

[trask]

@chalin @cartermp @austinlparker do you know of any prior art for keeping the registry up-to-date with instrumentations that we publish? (and should this be a goal?)

[cartermp]

Nothing I know of other than people updating entries 😬

[chalin]

No, but it is something that we can look into. Can you give one or a few examples of entries that are out-of-date?

[jaydeluca]

@svrnm are you using any kind of automated procedure for updates like https://github.com/open-telemetry/opentelemetry.io/pull/5625 or are you doing this work manually?

[svrnm]

@jaydeluca there are currently 2 things we do to keep things (semi)automatically updated:

• registry scanner is a tiny tool that scans most repos (including) java and generates some files from new entries. This is not automatic right now because those files need manual intervention
• https://github.com/open-telemetry/opentelemetry.io/blob/main/.github/workflows/scripts/update-registry-versions.sh#L64 updates the version from packages that have them from the maven registry. It's a fairly new addition, afaik there are currently 2 or 3 java packages with version annotation

I have this outstanding community proposal to rework the registry data: https://github.com/open-telemetry/community/pull/2246

[jaydeluca]

Fixed by #14697 (and some other things I have in the works)