Yes, it’s a bit confusing indeed. I don’t know why GitHub doesn’t update the timestamp. But if you look at the commit id of the release, you can verify it points to the new changes.
I did try to figure this out on my own (I even Googled it! :D) but came up empty. Now that we’ve got this sorted out, I need you to make a small change to your properties file PR (commented in GH) and then we can move foward.
Just one question: why does the plugin shows in the Marketplace with version 1.0.3-SNAPSHOT? I’m trying to find that in code or manifests to see where we missed the change but couldn’t find it.
Thanks Felipe! I’ve been checking and I can’t find any reference to a version other than 1.0.5 in manifest files and poms. Maybe the plugin jar was cached on your side and it’s still using the previous build? Don’t know, just trying to figure out where that is coming from
I think I’ve figured this out. It’s (as usual) a combination of several things:
the manifest for your 1.0.3 version includes this property: Plugin-Display-Version: 1.0.3-SNAPSHOT
the download for your 1.0.5 version is named exactly the same as for your 1.0.3 version: quboo-sonar-plugin.jar (versus, e.g. sonar-php-plugin-3.1.1.4762.jar)
the job that generates the Marketplace &etc data files pull all the downloads into the same directory and uses the jars’ manifest files as data sources.
Because your versions’ downloads have the same name, you’re experiencing last-saved-wins; the 1.0.3 download is providing metadata for both of your versions, hence the wrong display version. I suggest we scrap the 1.0.5 version, and you create a 1.0.6 version with a uniquely named jar and submit another PR.