I think I know the problem.
Current master creates multiple MavenProject instances for the same
parent pom, while 3.0.5 reused the same instance. I have not looked how
hard this will be to fix yet.
In, more generally, MavenProject implementation is far from efficient.
For example, each instance holds two copies of project Model and
absolutely no model element reuse. For example, the same <dependency>
element defined in a parent pom will be represented as distinct object
instance in each child project. This is something we've known in m2e for
long time, but optimizing this will quite tricky especially if we want
to maintain backwards compatibility and keep model instances mutable.
--
Regards,
Igor
On 2014-10-16, 13:30, Jörg Schaible wrote:
Hi Igor,
Igor Fedorenko wrote:
You can zip and email it to me directly or share it on github, dropbox
or google drive and send me the link. I am flexible :-)
I've sent the small one directly ...
Cheers,
Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
