Réda Housni Alaoui created MNG-6645:
---------------------------------------
Summary: Maven caches missing release dependencies, so further
builds fail without checking the repo until the cache expires or -U is included
to flush the cache
Key: MNG-6645
URL: https://issues.apache.org/jira/browse/MNG-6645
Project: Maven
Issue Type: Bug
Reporter: Réda Housni Alaoui
I have been experiencing this behaviour for many years.
Today, I decided to open an issue about it.
When Maven fails to resolve a release dependency, it caches the fact that it
did not find it with this kind of message:
{code:java}
16:42:13 [ERROR] Plugin com.cosium.code:maven-git-code-format:1.23 or one of
its dependencies could not be resolved: Failure to find
com.cosium.code:maven-git-code-format:jar:1.23 in
https://repo.cosium.com/repository/all was cached in the local repository,
resolution will not be reattempted until the update interval of cosium-repo-all
has elapsed or updates are forced -> [Help 1]{code}
In my example, I cut a new artifact release to Maven Central. Once the release
is done, you must wait a few minutes or hours before being able to pull the
artifact from Maven Central. I forgot and didn't wait enough time.
Because of this mistake, our CI machine cached the "failure". The only way to
make the CI build work again is to ssh the CI machine and remove the incorrect
part from the local maven repository.
I think that Maven should never cache the resolution failure, it should retry
the resolution on each build.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
