You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
By design, the version should be sorted in reverse order of the semantic version, with the latest version on the top. If it's not a semantic version, sort in alphabetical order.
Semantic version format is major.minor.patch-identifier. BUT, for Spring-boot artifacts, official versions are major.minor.patch.identifier, e.g. "2.1.0.RELEASE". So finally the versions are sorted in alphabetical order.
My suggestion is to have a more robust version parser. E.g. split by . and -, and numeric values are recognized as major, minor, patch by turns. The rest part can be regarded as identifier.
The text was updated successfully, but these errors were encountered:
By design, the version should be sorted in reverse order of the semantic version, with the latest version on the top. If it's not a semantic version, sort in alphabetical order.
Semantic version format is
major.minor.patch-identifier
. BUT, for Spring-boot artifacts, official versions aremajor.minor.patch.identifier
, e.g. "2.1.0.RELEASE". So finally the versions are sorted in alphabetical order.My suggestion is to have a more robust version parser. E.g. split by
.
and-
, and numeric values are recognized as major, minor, patch by turns. The rest part can be regarded as identifier.The text was updated successfully, but these errors were encountered: