Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
3.0
-
None
Description
As I tried to explain in MARTIFACT-25, maven always checks for missing release artifacts and even though this does not have noticeable performance impact on regular maven cli builds (unless, -fn, I guess), this does cause significant performance problems in embedding applications like m2e in some scenarios.
To demonstrate the problem, I've added new (and currently disable) testResolveMissingArtifact to P001EmbedderTest performance regression test suite. On my development machine, running doTestResolveMissingArtifact(delay=false) takes ~2ms on average. Running doTestResolveMissingArtifact(delay=true), on the other hand, takes ~202ms, which means that remote repository is accessed twice during each doTestResolveMissingArtifact(delay=true) call.
Attachments
Issue Links
- is duplicated by
-
MNG-1902 track attempted downloads and only re-attempt on certain intervals
- Closed
-
MNG-2194 no downloading attempts of non-existing artifact
- Closed
- is related to
-
MNG-3421 artifacts not found in any repo are continually rechecked in subsequent builds
- Closed
-
MNG-3436 updateInterval checking for releases causes major slow-down
- Closed
- relates to
-
MNG-4142 Maven doesn't try to download a dependency when it already exists a version with classifier locally
- Closed
-
MNG-2443 Don't download pom if artifact is already in the local repository
- Closed
-
MNG-4592 Snapshot artifacts that could not be downloaded due to communication problems are "blacklisted" for a day by default.
- Closed
-
MNG-3035 Maven caches missing snapshot dependencies, so further builds fail without checking the repo until the cache expires or -U is included to flush the cache
- Closed