Hochan Kang created COMMONSSITE-181:
---------------------------------------
Summary: Incorrect versioning.latest value in Commons IO Maven
metadata
Key: COMMONSSITE-181
URL: https://issues.apache.org/jira/browse/COMMONSSITE-181
Project: Apache Commons All
Issue Type: Bug
Components: Commons Build
Reporter: Hochan Kang
Attachments: image-2025-11-11-23-05-21-162.png
It seems that the {{maven-metadata.xml}} file for *Apache Commons IO* contains
an incorrect {{versioning.latest}} value.
The file at:
[https://repo.maven.apache.org/maven2/commons-io/commons-io/maven-metadata.xml]
currently shows:
{code:java}
<versioning>
<latest>20030203.000550</latest>
</versioning> {code}
!image-2025-11-11-23-05-21-162.png|width=1156,height=637!
This value appears to point to an old legacy version, while the latest release
should be 2.21.0 (as listed on Maven Central and the Commons IO website).
This incorrect metadata can cause build issues for Maven-based projects that
rely on the "latest" version resolution instead of specifying an explicit
version.
----
*Steps to Reproduce:*
Create a simple Maven project without specifying a version for commons-io
dependency.
Run mvn dependency:tree or build the project.
Maven resolves commons-io:commons-io:20030203.000550 as the latest version.
----
*Expected Result:*
versioning.latest should reflect the most recent stable release, e.g. 2.21.0.
*Actual Result:*
versioning.latest is set to 20030203.000550, which causes Maven to download an
outdated version and may lead to compilation errors.
----
*Additional Info:*
This issue affects Maven projects that omit an explicit version for Commons IO
dependencies.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
