You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Michael Osipov (Jira)" <ji...@apache.org> on 2021/10/16 11:53:00 UTC
[jira] [Comment Edited] (CLI-310) Purge release version
20040117.000000 from Maven Central
[ https://issues.apache.org/jira/browse/CLI-310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17429547#comment-17429547 ]
Michael Osipov edited comment on CLI-310 at 10/16/21, 11:52 AM:
----------------------------------------------------------------
This is annoying, agreed, but Maven Central is almost immutable. [~brianf], I guess we cannot really do anything about this, can we?
was (Author: michael-o):
This is annoying, agreed, but Maven Central is almost immutable. [~dexwest], I guess we cannot really do anything about this, can we?
> Purge release version 20040117.000000 from Maven Central
> --------------------------------------------------------
>
> Key: CLI-310
> URL: https://issues.apache.org/jira/browse/CLI-310
> Project: Commons CLI
> Issue Type: Task
> Reporter: Markus Spann
> Priority: Minor
>
> How did commons-cli "release version" 20040117.000000 make it into Maven Central?
> It's been there for as long as I can remember.
> It would not bother any of us if this version did not always show up as the most recent/latest/bleeding edge release. Even though it's ancient and noone would want to use it of course.
> This effect is due to this version not following the commons-cli version scheme and due to the way Maven sorts version strings.
> A small use case to illustrate:
>
> {code:java}
> mvn versions:display-dependency-updates
> {code}
>
> {code:java}
> [INFO] The following dependencies in Dependencies have newer versions:
> [INFO] commons-cli:commons-cli ....................... 1.4 -> 20040117.000000
> {code}
> I understand that purging release artifacts from Central may not be simple. Yet it would be so much appreciated if someone with the corresponding know-how and access could take care of it. Thanks a million!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
Re: [jira] [Comment Edited] (CLI-310) Purge release version
20040117.000000 from Maven Central
Posted by Alex Herbert <al...@gmail.com>.
This is a problem that can at least be fixed on the github README page
so the badge points to the latest version. I have updated the badge to
use 'gav=true' to bypass semver issues [1]. The badge now points to
1.4.
Alex
[1] https://github.com/softwaremill/maven-badges
On Sat, 16 Oct 2021 at 12:53, Michael Osipov (Jira) <ji...@apache.org> wrote:
>
>
> [ https://issues.apache.org/jira/browse/CLI-310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17429547#comment-17429547 ]
>
> Michael Osipov edited comment on CLI-310 at 10/16/21, 11:52 AM:
> ----------------------------------------------------------------
>
> This is annoying, agreed, but Maven Central is almost immutable. [~brianf], I guess we cannot really do anything about this, can we?
>
>
> was (Author: michael-o):
> This is annoying, agreed, but Maven Central is almost immutable. [~dexwest], I guess we cannot really do anything about this, can we?
>
> > Purge release version 20040117.000000 from Maven Central
> > --------------------------------------------------------
> >
> > Key: CLI-310
> > URL: https://issues.apache.org/jira/browse/CLI-310
> > Project: Commons CLI
> > Issue Type: Task
> > Reporter: Markus Spann
> > Priority: Minor
> >
> > How did commons-cli "release version" 20040117.000000 make it into Maven Central?
> > It's been there for as long as I can remember.
> > It would not bother any of us if this version did not always show up as the most recent/latest/bleeding edge release. Even though it's ancient and noone would want to use it of course.
> > This effect is due to this version not following the commons-cli version scheme and due to the way Maven sorts version strings.
> > A small use case to illustrate:
> >
> > {code:java}
> > mvn versions:display-dependency-updates
> > {code}
> >
> > {code:java}
> > [INFO] The following dependencies in Dependencies have newer versions:
> > [INFO] commons-cli:commons-cli ....................... 1.4 -> 20040117.000000
> > {code}
> > I understand that purging release artifacts from Central may not be simple. Yet it would be so much appreciated if someone with the corresponding know-how and access could take care of it. Thanks a million!
>
>
>
> --
> This message was sent by Atlassian Jira
> (v8.3.4#803005)