[jira] [Commented] (CLI-310) Purge release version 20040117.000000 from Maven Central

["Herve Boutemy (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CLI-310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17540162#comment-17540162 ] 

Herve Boutemy commented on CLI-310:
-----------------------------------

{quote}How did commons-cli "release version" 20040117.000000 make it into Maven Central?
{quote}
from name and date in the directory [https://repo.maven.apache.org/maven2/commons-cli/commons-cli/] , it seems it's something that was published between 2004 and 2005, probably with Maven 1, on the repository maintained by Maven PMC (I was not yet there, I don't know precisely how it was done at that time...): probably checks were not as strong at that time as they are for 10+ years

I think that if Commons PMC wants this artifact to be removed, they should ask as owners of these artifact: I'd prefer not having Sonatype accept anybody's request

(I won't dig on why this went unnoticed for 17 years but becomes a problem nowadays)

> 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.20.7#820007)