Re: [io] can we delete release 20030203.000550 in maven central?
Hello, I don't think the "largest version detect" is done on the Repo. Maven central offers all available versions in the metadata, and Maven locally resolves the highest version (when latest is used) Also since Maven central is supposed to be immutable a new coordinate sooner or later is the only way to avoid everybody having to manually block the offender. (And of course always specifying a specific version in POMs) Bernd -- http://bernd.eckenfels.net Von: Gary Gregory Gesendet: Sunday, June 14, 2020 4:58:27 PM An: Commons Developers List Betreff: Re: [io] can we delete release 20030203.000550 in maven central? I suppose you can ask Sonatype to offer a sort by release date feature on that kid of query result. Gary On Sun, Jun 14, 2020, 10:44 Melloware Inc wrote: > Gary, > > Maven Central Search does not. Se ethos URL: > https://search.maven.org/search?q=g:commons-io > > Commons-IO 20030203.000550 is shown as the latest version incorrectly. > > Mello > > On Sun, Jun 14, 2020 at 10:29 AM Gary Gregory > wrote: > > > 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 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 > > 1000+ > > > in our life, but... > > > That just feels strange. > > > > > > > > > Gary Gregory 于2020年6月14日周日 下午9:52写道： > > > > > > > On Sun, Jun 14, 2020 at 9:51 AM Xeno Amess > > 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 于2020年6月14日周日 下午9:39写道： > > > > > > > > > > > On Sun, Jun 14, 2020 at 6:40 AM Xeno Amess > > > > 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 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > == > Melloware > melloware...@gmail.com > http://melloware.com > == >
Re: [io] can we delete release 20030203.000550 in maven central?
I suppose you can ask Sonatype to offer a sort by release date feature on that kid of query result. Gary On Sun, Jun 14, 2020, 10:44 Melloware Inc wrote: > Gary, > > Maven Central Search does not. Se ethos URL: > https://search.maven.org/search?q=g:commons-io > > Commons-IO 20030203.000550 is shown as the latest version incorrectly. > > Mello > > On Sun, Jun 14, 2020 at 10:29 AM Gary Gregory > wrote: > > > 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 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 > > 1000+ > > > in our life, but... > > > That just feels strange. > > > > > > > > > Gary Gregory 于2020年6月14日周日 下午9:52写道： > > > > > > > On Sun, Jun 14, 2020 at 9:51 AM Xeno Amess > > 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 于2020年6月14日周日 下午9:39写道： > > > > > > > > > > > On Sun, Jun 14, 2020 at 6:40 AM Xeno Amess > > > > 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 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > == > Melloware > melloware...@gmail.com > http://melloware.com > == >
Re: [io] can we delete release 20030203.000550 in maven central?
Gary, Maven Central Search does not. Se ethos URL: https://search.maven.org/search?q=g:commons-io Commons-IO 20030203.000550 is shown as the latest version incorrectly. Mello On Sun, Jun 14, 2020 at 10:29 AM Gary Gregory wrote: > 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 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 > 1000+ > > in our life, but... > > That just feels strange. > > > > > > Gary Gregory 于2020年6月14日周日 下午9:52写道： > > > > > On Sun, Jun 14, 2020 at 9:51 AM Xeno Amess > 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 于2020年6月14日周日 下午9:39写道： > > > > > > > > > On Sun, Jun 14, 2020 at 6:40 AM Xeno Amess > > > 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 > > > > > > > > > > > > > > > > > > > > > -- == Melloware melloware...@gmail.com http://melloware.com ==
Re: [io] can we delete release 20030203.000550 in maven central?
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 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 1000+ > in our life, but... > That just feels strange. > > > Gary Gregory 于2020年6月14日周日 下午9:52写道： > > > On Sun, Jun 14, 2020 at 9:51 AM Xeno Amess 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 于2020年6月14日周日 下午9:39写道： > > > > > > > On Sun, Jun 14, 2020 at 6:40 AM Xeno Amess > > 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 > > > > > > > > > > > > > > >
Re: [io] can we delete release 20030203.000550 in maven central?
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 1000+ in our life, but... That just feels strange. Gary Gregory 于2020年6月14日周日 下午9:52写道： > On Sun, Jun 14, 2020 at 9:51 AM Xeno Amess 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 于2020年6月14日周日 下午9:39写道： > > > > > On Sun, Jun 14, 2020 at 6:40 AM Xeno Amess > 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 > > > > > > > > > >
Re: [io] can we delete release 20030203.000550 in maven central?
On Sun, Jun 14, 2020 at 9:51 AM Xeno Amess 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 于2020年6月14日周日 下午9:39写道： > > > On Sun, Jun 14, 2020 at 6:40 AM Xeno Amess 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 > > > > > >
Re: [io] can we delete release 20030203.000550 in maven central?
Or if we should create commons-io2 and commons-BeanUtils2 like what we've done in lang3, as @John Patrick suggested? Gary Gregory 于2020年6月14日周日 下午9:39写道： > On Sun, Jun 14, 2020 at 6:40 AM Xeno Amess 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 > > >
Re: [io] can we delete release 20030203.000550 in maven central?
On Sun, Jun 14, 2020 at 6:40 AM Xeno Amess 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 >
Re: [io] can we delete release 20030203.000550 in maven central?
"update toolchain" here means idea's package plugin, which seems have no
way to set up rules like rules in versions-maven-plugin.
[image: image.png]
Of course we can try to only use versions-maven-plugin.
But a setting like that just hides problem, it does not solve the problem.
The real problem is that "An older version have a larger version number
than a newer version"[1].
And nearly all rules about versioning forbids that [1].
Rob Spoor 于2020年6月14日周日 下午7:03写道：
> On 14/06/2020 12:40, Xeno Amess 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?)
> > The same problem happened in BeanUtils, version 20030211.134440
>
> That's why you can use a set of rules with the Maven versions plugin:
> https://www.mojohaus.org/versions-maven-plugin/version-rules.html
>
> For instance, here's part of the rules I use:
>
> artifactId="commons-collections">
>
>
> 200[34]\d{4}.*
>
>
>
> In a similar way, you can exclude alpha, beta, release-candidate and
> milestone versions. You just need to find the proper regex.
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>
Re: [io] can we delete release 20030203.000550 in maven central?
On 14/06/2020 12:40, Xeno Amess 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?)
The same problem happened in BeanUtils, version 20030211.134440
That's why you can use a set of rules with the Maven versions plugin:
https://www.mojohaus.org/versions-maven-plugin/version-rules.html
For instance, here's part of the rules I use:
artifactId="commons-collections">
200[34]\d{4}.*
In a similar way, you can exclude alpha, beta, release-candidate and
milestone versions. You just need to find the proper regex.
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
Re: [io] can we delete release 20030203.000550 in maven central?
I keep thinking that too, and ended up just using a custom versions rule to ignore it. Other idea maybe change to GAV to; 1) org.apache.commons:commons-io 2) org.apache.commons:commons-io2 So starting to match the commons-lang3 approach. I find commons-lang3 is a really good pattern and is much easier, as it supports older and newer versions on the classpath at the same time without conflict. Allowed phased upgrades. And an upgrade to lang3 from lang is just a find/replace "org.apache.commons.lang." to "org.apache.commons.lang3." and ticket off the build process to check it worked. Hopefully they will keep the same style for lang4 and it will just be another find/replace upgrade when i choose. On Sun, 14 Jun 2020 at 11:40, Xeno Amess 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?) > The same problem happened in BeanUtils, version 20030211.134440 - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[io] can we delete release 20030203.000550 in maven central?
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?) The same problem happened in BeanUtils, version 20030211.134440
