bade7n opened a new pull request, #1691:
URL: https://github.com/apache/maven-resolver/pull/1691
In our CI pipelines we are encountering a substantial number of exceptions
like:
```
[main] [WARNING] Failed to read tracking file
'/home/builduser/.m2/repository/cached/central-proxy/org/apache/maven/wagon/wagon-provider-api/1.0-alpha-6/wagon-provider-api-1.0-alpha-6.jar.lastUpdated'
java.io.FileNotFoundException:
/home/builduser/.m2/repository/cached/central-proxy/org/apache/maven/wagon/wagon-provider-api/1.0-alpha-6/wagon-provider-api-1.0-alpha-6.jar.lastUpdated
(No such file or directory)
at java.io.FileInputStream.open0 (Native Method)
at java.io.FileInputStream.open (FileInputStream.java:219)
at java.io.FileInputStream.<init> (FileInputStream.java:157)
at org.eclipse.aether.internal.impl.DefaultTrackingFileManager.read
(DefaultTrackingFileManager.java:58)
...
```
These errors occur when a `.lastUpdated` tracking file is missing during
concurrent repository access, leading the build to fail even though the file
absence is harmless.
This patch introduces a safe fallback by catching `FileNotFoundException` in
`DefaultTrackingFileManager.read()`. Missing or concurrently removed tracking
files are now treated as non-fatal, preventing unnecessary build failures.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
