Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Duplicate
-
2.0.4
-
None
-
None
Description
There are many projects out there just providing their artifact without a pom (whether this is good or not is a different question). Now in this case m2 always tries to download a pom for those artifacts, even if the artifact itself is already in the local repository. And if you have several of those artifacts combined with more than one repository configured, then there are a lot of unnecessary download attempts.
I think this falls into the same category as changing a pom in the repository (which should be forbidden) - so if for the first time the artifact is downloaded no pom available, then there will never be a pom for this specific artifact.