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

Benedikt Waldvogel edited comment on IO-881 at 11/12/25 7:31 PM:
-----------------------------------------------------------------

The issue seems to be fixed now!  🎉

Big thanks to whoever fixed the latest version data in 
[https://repo1.maven.org/maven2/commons-io/commons-io/maven-metadata.xml] 🙏
Was it even an automated process?

FTR:

The previous version of maven-metadata.xml ({{{}lastUpdated=20251107184946){}}} 
defined latest version to be {{20030203.000550}} ❌
Now, the current version of maven-metadata.xml 
({{{}lastUpdated=20251112172346){}}} correctly defines the latest version to be 
{{2.21.0}} ✅
BTW: Even search.maven.org showed the wrong version:

!image-2025-11-12-20-16-36-498.png|width=244,height=166!

[~ggregory], [~b.eckenfels]: We probably talked past each other. This issue 
wasn’t about a two decades old version that shouldn’t be in Maven Central. This 
issue was about a very recent change (November 7th) that affected many but of 
course not all tools. Since even search.maven.org was affected, the impact was 
rather big IMO.
{quote}Publishing a new version will do nothing to change software the sorts 
based on version number instead of date. Sometimes sorting on the date is what 
you want, sometimes not […]
[~ggregory]
{quote}
My suggestion was fixing the latest version metadata in 
[https://repo1.maven.org/maven2/commons-io/commons-io/maven-metadata.xml]. 
Software that picks the latest version based on sorting is wrong since two 
decades, sure. But this was about a new issue that (even) affected tools that 
_don’t_ pick the version by sorting.
{quote}And as already mentioned this is not a new thing, that version is broken 
since a very Long time […]
[~b.eckenfels]
{quote}
Actually this issue is/was about a new thing ;)


was (Author: bwaldvogel):
The issue seems to be fixed now!  🎉

Big thanks to however fixed the latest version data in 
[https://repo1.maven.org/maven2/commons-io/commons-io/maven-metadata.xml] 🙏
Was it even an automated process?

FTR:

The previous version of maven-metadata.xml ({{{}lastUpdated=20251107184946){}}} 
defined latest version to be {{{}20030203.000550{}}} ❌
Now, the current version of maven-metadata.xml 
({{{}lastUpdated=20251112172346){}}} correctly defines the latest version to be 
{{{}2.21.0{}}} ✅
BTW: Even search.maven.org showed the wrong version:

!image-2025-11-12-20-16-36-498.png|width=244,height=166!

[~ggregory], [~b.eckenfels]: We probably talked past each other. This issue 
wasn’t about a two decades old version that shouldn’t be in Maven Central. This 
issue was about a very recent change (November 7th) that affected many but of 
course not all tools. Since even search.maven.org was affected, the impact was 
rather big IMO.
{quote}Publishing a new version will do nothing to change software the sorts 
based on version number instead of date. Sometimes sorting on the date is what 
you want, sometimes not […]
[~ggregory]
{quote}
My suggestion was fixing the latest version metadata in 
[https://repo1.maven.org/maven2/commons-io/commons-io/maven-metadata.xml]. 
Software that picks the latest version based on sorting is wrong since two 
decades, sure. But this was about a new issue that (even) affected tools that 
_don’t_ pick the version by sorting.

{quote}And as already mentioned this is not a new thing, that version is broken 
since a very Long time […]
[~b.eckenfels]
{quote}
Actually this issue is/was about a new thing ;)

> 20030203.000550 is now latest version in Maven
> ----------------------------------------------
>
>                 Key: IO-881
>                 URL: https://issues.apache.org/jira/browse/IO-881
>             Project: Commons IO
>          Issue Type: Wish
>    Affects Versions: 2.21.0
>            Reporter: Alexander Veit
>            Priority: Minor
>         Attachments: image-2025-11-12-16-31-57-683.png, 
> image-2025-11-12-20-16-36-498.png
>
>
> With 2.21.0 the latest version in Maven has changed to 
> `{color:#000000}20030203.000550{color}` which is wrong.
>  
> See https://repo1.maven.org/maven2/commons-io/commons-io/maven-metadata.xml



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to