commit | d0cd1dbaf370f7e7602c21ed653abc1e4f825f0a | [log] [tgz] |
---|---|---|
author | Mickael Istria <mistria@redhat.com> | Thu Nov 22 14:38:36 2018 +0100 |
committer | Mickael Istria <mistria@redhat.com> | Thu May 09 07:05:15 2019 -0400 |
tree | b369a92985c8f3803678bb9d5c03728808e7c21a | |
parent | c9e4eb3dd7ca4585b93e226d6258a3cb9f9f4170 [diff] |
Bug 515668 - Introduce APIs to group MavenProject reads Using ProjectBuilder.build(singlePom...) has a speed and memory complexity of O(depth(project)) where depth(project) is the number of parents (recursively). Iterating on this over N projects lead to a pseudo-quadratic cost O(N*maxProjectDepth) where maxProjectDepth can be up to N-1. Instead, we introduce APIs that take advantage ProjectBuilder.build(multiplePom...) which has a complexity of O(N). For Apache Camel that is 700+ modules, these new APIs instantiate 700+ MavenProject instead of ~4000 (since many modules have a depth of 5/6) like legacy API do. Change-Id: Ica74542eb8db6833de3b796bfad8c07c2ae9b002 Signed-off-by: Mickael Istria <mistria@redhat.com>
This is the m2eclipse-core repository