I'm not sure what you are using, but Maven Central sorts by release date: https://search.maven.org/artifact/commons-io/commons-io
Gary On Sun, Jun 14, 2020 at 9:56 AM Xeno Amess <xenoam...@gmail.com> wrote: > It is strange to have an older version have a larger major version number > than a newer version. > Of course we might never witness a major version whose number be 10000000+ > in our life, but... > That just feels strange. > > > Gary Gregory <garydgreg...@gmail.com> 于2020年6月14日周日 下午9:52写道： > > > On Sun, Jun 14, 2020 at 9:51 AM Xeno Amess <xenoam...@gmail.com> wrote: > > > > > Or if we should create commons-io2 and commons-BeanUtils2 like what > > > we've done in lang3, as @John Patrick suggested? > > > > > > > Why? > > > > Gary > > > > > > > > > > Gary Gregory <garydgreg...@gmail.com> 于2020年6月14日周日 下午9:39写道： > > > > > > > On Sun, Jun 14, 2020 at 6:40 AM Xeno Amess <xenoam...@gmail.com> > > wrote: > > > > > > > > > every time my update tool chain thinks 20030203.000550 is a greater > > > > version > > > > > than 2.7 (actually it is, if see it in number). > > > > > So have we some way to delete it from maven central? (or rename > it?) > > > > > > > > > > > > > Yes, but we will never do that. That would break applications > depending > > > on > > > > that version. There are rare cases where releases may be withdrawn. > > > > > > > > Gary > > > > > > > > > > > > > The same problem happened in BeanUtils, version 20030211.134440 > > > > > > > > > > > > > > >
