how/when does https://grails.apache.org/plugins.html get updated? Our freshly released grails-export plugin does not (yet) show up there

There is a GitHub Action running a couple of times every day.

ah, yes, thx. So I have to update the data, create a PR and then everything will be fine after it is merged?

Yep

the plugin changed coords, so should I move the whole file to the new location and provide override properties for the relevant old versions?

Yes,

git move

the file and update coords, maven-repo,.. the GH Action will update the versions

So, can I leave the versions empty and they will be populated with the actual release data?

Yes, the versions are read from the maven-metadata.xml file published to Maven Central

Only the new coordinates in the yml file, the plugins site only show the latest version.

@Thomas Rasmussen This is not correct, all versions are shown on the plugin page. The version component is a dropdown. For example look at the

grails-mail

plugin that has changed coords and repos. All versions are listed.

The plugin changed group and name. Would it make sense to keep the old

org.grails.plugins:export

for Grails 3.x and

io.github.gpc:grails-export

for 7.x?

No, it should be migrated to the new coords.

I suggested updating the readme in the VCS repo with info about the old versions

I think we could do both: • Update the documentation/readme in the repo • Keep at least the previous release with the old coordinates for all the 3.x-6.x users in the metadata

The plugins page has updated now https://grails.apache.org/plugins/tags/export.html

not specific to the export plugin: the version selector does not work for me. Can anyone reproduce?

Well, it is not technically a selector. Only a panel, so you cannot switch versions. It could be enhanced to be a selector, if that would be useful.

It it was a selector, the dependency could change with it, and for the grails-export it could show

org.grails.plugins:export:2.0.0

(available in the metadata?) since it's different than the current

io.github.gpc:grails-export:7.0.0

first I find it misleading to have to dropdown-selector that "does nothing" and second it would be really useful for artifacts that changed their coordinates over time

It's FOSS! Pull requests are always welcomed 😉

irst I find it misleading to have to dropdown-selector that "does nothing" and second it would be really useful for artifacts that changed their coordinates over time

Yes, I agree! But it was a pretty big undertaking to re-hauling that whole plugin metadata repository and plugin page. I had to stop somewhere to get back to more pressing things.

sure, it can be improved over time

it is much more important to have an actively developed framework and all the needed plugins than a nice fully featured plugin page...