tweaking at eclipse (memory settings or alike) itself did not solve my
problem. so i gave http://maven.apache.org/archiva/ a try and now it
goes much quicker.
on command line about 30% and within m2eclipse 500% (!) quicker, so my
guess that m2eclipse spends exorbitantly long on dependency resolution
(in comparison to command-line) was right.
[EMAIL PROTECTED] schrieb:
hi,
m2eclipse works fine for me from the functional point of view.
though when coming to projects with many dependencies , it takes very
long for maven to get the Build done (either through Project->Clean...
or pom.xml save).
following preconditions:
-using eclipse europe (http://www.eclipse.org/downloads/ 140MB) with
additional sublipse and m2eclipse (0.0.12.20071107).
-winXP, 3GB RAM, Pentium4 3,4 GHz
-only one project in workspace (pom inclusion of 61 dependencies ,
direct and transitive)
measurement1:
-no eclipse.exe args:
---> time taken: 90 sec.
measurement2:
-eclipse.exe args: (-vmargs -Xms512M -Xmx1408M -Xss2M -Xfuture
-XX:PermSize=64M -XX:MaxPermSize=128M -Dcom.sun.management.jmxremote)
---> time taken: 45 sec.
measurement3:
-running 'mvn compile' on command-line (maven 2.0.7)
---> time taken: 22 sec
i perceive these 45 sec from m2eclipse very long and this makes my
work inside IDE slow down noticeably (opening, reopening projects,
working directly with pom.xml, etc.). in contrast the command line
maven is much quicker.
has anybody suggestions/ideas of tweaking eclipse with m2eclipse plugin?
--
manuel aldana
[EMAIL PROTECTED]
homepage: www.aldana-online.de
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
