maven always checks missing release artifacts
---------------------------------------------
Key: MNG-4343
URL: http://jira.codehaus.org/browse/MNG-4343
Project: Maven 2
Issue Type: Bug
Components: Artifacts and Repositories
Affects Versions: 3.0
Reporter: Igor Fedorenko
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.
https://svn.sonatype.org/m2eclipse/sandbox/trunk/maven-performance-tests/src/test/java/org/apache/maven/performance/tests/p001/P001EmbedderTest.java
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
