Manuel,
First of all, we took out "Update Dependencies" out of the JDT build
cycle and it is now available as a separate action in the Maven popup
menu. That is why project Clean is now much faster and it also allowed
us to speed up the dependency resolution probably to the order of
magnitude comparing to the previous release and there are still few
places that could be improved.
You can watch the Progress view and Maven console (see drop down in
the Eclipse Console view) to see what is happening there. If you have
download sources and javadocs enabled in the project dependencies it
might be downloading those, but then it should be much faster on the
second update.
Anyways, if you decide to submit a JIRA for this, please make sure to
attach the test project that would allow us to reproduce this issue and
also see this wiki page for additional hints.
http://docs.codehaus.org/display/M2ECLIPSE/Reporting+Issues
Thanks
Eugene
[EMAIL PROTECTED] wrote:
i installed it without problems, so i could have a try. my first
impressions:
the Project->Clean... speeded up significantly, performance close to
the command line version :)
what takes quite long on the other hand is closing and opening
projects. following workspace:
-Common
-A uses Common
-B uses Common
-C uses Common
when closing Common project a eclipse task starts (Updating Maven
Dependencies) and takes very long (it is done for each project A,B,C).
regarding this i think it is a great improvement that dependent
projects are notified when projects are getting opened or closed.
never the less i need to wait quite long (around one minute) for
'Updating Maven Dependencies' eclipse task to be finished.
i had a look at jira but did not find an entry for that. has anybody
had similar experience with 0.9.0 version?
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
