Fix plugin badge showing an outdated version

[TWiStErRob]

Also would you mind editing 4.0.0 and adding this list item:

• Dependency coordinates changed from com.github.gmazzo:gradle-buildconfig-plugin to com.github.gmazzo.buildconfig:plugin; Gradle Plugin ID and Marker stayed the same.

[gmazzo]

Thanks for catching this! I've just updated the URL with the latest shield.io generated code for the badge

[TWiStErRob]

You removed the link, it's just an image now.

[gmazzo]

Yeah, noted that too. I've fixed it already. Thanks!

[TWiStErRob]

Nice! What do you think about updating the release notes?

[gmazzo]

Nice! What do you think about updating the release notes?

Hi, sorry. What is wrong with the release notes? I didn't note anything wrong, but it may be.

I didn't published a new version because there is no change on the code, releases noted including this change will be generated automatically when I release it

[TWiStErRob]

I think this should be added to 4.0.0 (mentioned in OP)

• Dependency coordinates changed from com.github.gmazzo:gradle-buildconfig-plugin to com.github.gmazzo.buildconfig:plugin; Gradle Plugin ID and Marker stayed the same.

Because many users are using the artifacts directly (implementation in buildSrc/includeBuild), and they won't get an update from automated tools, because of not using the marker artifact. When noticing there's a new version (now that the badge shows latest), they'll try to bump the version and fail. Even if they read through the release notes, they won't know that the artifact coordinates changed, unless the above is mentioned. I went through this cycle myself twice already.

[gmazzo]

Alright, done!

I usually use the <pluginId>:<pluginId>.gradle.plugin convention coordinates for this, that's why I misted. Thanks!

[TWiStErRob]

Thank you!

I know, I do too now, but I only learned about that few months ago even though I've been a fan of Gradle for years. For empirical fun:

• old plugin artifact 106
• new plugin artifact 22
• eternal plugin marker 27

Of course these exclude split/programmatic references like the pattern you had above.

Bonus: I forgot about this, but I noticed while searching. When we use content restricted repositories we have to use both! Example.

I think this is because even the portal is not using the marker: https://plugins.gradle.org/plugin/com.github.gmazzo.buildconfig

[gmazzo]

Nice, I was not aware how spread this plugin was over the open-source community.