Same thing here. It was better with m2eclipse 0.10, but this has some other major issues.
Things to improve on 0.12 imo (applicable for a multimodule maven setup): * snapshots are always checked for updates, even when <snapshotPolicy>never</snapshotPolicy> is added to all repositories * when cleaning all projects, for each projects, all dependenat project poms are read / parsed analyzed. In Progress view it says: updating (projectname): reading (projectname)/pom.xml. This takes about 0.75s per pom.xml. I think it should cache this, so that on a refresh/ clean this delay happens only once per dependency-project On Feb 4, 2008 2:15 PM, VUB Stefan Seidel <[EMAIL PROTECTED]> wrote: > Hi, > > I also suspect that the m2 version embedded in the plugin has a > different strategy for resolving artifacts. I struggled to create a test > project but I was not able to find the cause. Here, we overwrite the > central repository to point to a local proxy, but in Eclipse, maven > tries to resolve artifacts from completely different repos (like > apache-snapshots etc.). I don't know why, and the 2.0.8 never does that. > > regards, > > Stefan > > [EMAIL PROTECTED] wrote: > > 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? > >> > > > > > > -- > best regards, Stefan Seidel software developer ________________________ > VUB Printmedia GmbH Chopinstraße 4 D-04103 Leipzig Germany tel. +49 > (341) 9 60 50 07 fax. +49 (341) 9 60 50 92 mail. [EMAIL PROTECTED] web. > www.vub.de HRB Köln 24015 UStID DE 122 649 251 GF Dr. Achim Preuss > Neudorf, Dr. Christian Preuss Neudorf > > --------------------------------------------------------------------- > To unsubscribe from this list please visit: > > http://xircles.codehaus.org/manage_email > > -- Squins IT Solutions Kees van Dieren Oranjestraat 23 2983 HL Ridderkerk Phone: +31 180 41 45 20 Mobile: +31 6 30 41 38 41 www: http://squins.com
