I prepare more statistics:
I tested the problem on two projects:
* it0124 (from MNG-1323) ( 3 artifacts)
* medium_real_project (40 artifacts)
The current version on maven (2.0.8-SNAPSHOT) with "-X -o":
it0124 : 9 seconds; 8 seconds; 9 seconds (all didn't finish
because of the MNG-1323 issue)
there were 24 asks to cache (6 failed and 18 found
the pluginDescriptor in cache)
medium_real_project) - (53; 49; 53; 50 seconds) ( 496 asks = 15
failures +481 found in casche)
The version 2.0.8-SNAPSHOT with commented cache:
* it0124: 14;13;14 seconds - succeeded
* medium_real_project: (153,151,150,151 seconds) - YES - THREE
TIME LONGER - I am also in shock
So I am sure - we cannot just comment cache.
I there are still 3 possibilities:
a) (new one) Cache only plugins without additional (from user's
project pom.xml) dependencies. Most of plugins (and the most often
called) are without additional "dependencies".
b) Check each received answer from cache if dependencies matches
(and if not) change the cached entry.
c) Enlarge plugin's id for cache (by adding dependencies's hashcode) ...
(John Casey: The amount of plugins is generally "constant" and
low (15) - so I don't see the "memory" problem).
Thanks,
Piotr
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
