Json Java package is mis-reporting

[Gavin Mogan]

I think https://www.versioneye.com/java/org.json:json/20160212 is the latest version, but it keeps saying 5.0.5 is newer

To me, 20160212 is a major version number, so should be way higher than 5

[Robert Reiz]

Hi @halkeye. I see the problem. VersionEye is supporting semantic versioning. A string representation of a Date is not semantic versioning and doesn't have any semantic meaning. I'm not sure why but especially the Java community is very slow with adopting semver.

VersionEye is open source and the software which is sorting the version strings is here: https://github.com/versioneye/naturalsorter. Some Java projects used the time stamps in the past and they switched to semver. If we change the implementation that way that time stamps are considered higher than semver numbers than that will cause problems with other Java projects which moved from time stamps to semver. At this point there is conflict here. I'm open for solutions. Any ideas how to deal with this?

[Gavin Mogan]

I certainly don't have a good solution for this.

json looks like it compounds the issue by having the older versions actually semver but the newer ones dated.

Is there an override or special case? Can the older semver ones be blacklisted?