David,
When you close project, JDT rebuild anything that depended on it, and
that triggers refresh for the classpath container, i.e. replace
reference to depended project into jar from a local Maven repository.
The latter may trigger some downloading in case if required jars are not
in the local repository, but that downloading only happen once.
Also note that if you have "download sources/javadoc" option enabled
it will slow things down, which can be quite noticeable for large
projects (especially if there are no source or javadoc available from
remote repositories), so we generally recommend to not keep that option
enabled all the time. There is a JIRA issue already to improve this and
we'll look at it at some point.
Thanks
Eugene
David Balazic wrote:
I just updated form eclipse 3.1.2/m2eclipse 0.0.9 to 3.3.0/0.0.12 and
see behavior that I don't like.
I have about 10 projects open (all maven projects), that depend on
each other.
If I close one, a build frenzy breaks out that last up to a minute,
with maven downloading dependencies and so.
In 0.0.9, the closing of a project was a one second operation. Is
there a way to get back the old behavior ?
I looked thru options, but did not find anything.
(sorry if this is because of the new eclipse and not of the maven plugin)
Regards,
David
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
