Just to get experience, what size was it? The biggest project I have done so far with Exadel, was a shop backend, which had around 50-100 struts jsps subpages, integrated tiles, Hibernate with around 30 tables and the usual thing you can expect (Tomcat etc...)
Exadel 3.0.4 was sometimes flakey and sometimes locked but you could work with it and the progress was very good. An occasional clean was mandatory, but did not really cause problems. Given the fact that 3.0.4 was based under a rather flaky WTP0.7 I guess the new version would cause much less problems. The biggest project I currently have in MyEclipse is a legacy project which has a few hundred jsp pages, probably 200.000 locs in java an integrated axis 1.0 and a few other things, like several hundred velocity templates. MyEclipse swallows a little bit but basically working with it is possible. The main problem I have is the code preview in JSPs integrated which is dog slow at this project size, but this sort of is a known issue which has not been fixed totally yet (MyEclipse probably also waits for the WTP to progress like everyone) I tend to edit jsps with a different editor and already thought about splitting the project. The only real downside of projects of this size is, that a full compile takes ages because the japser compiler is dog slow, which all those plugins seem to use. I doubt the new jikes jasper will be faster which is now integrated in Tomcat, because the slownewss seems to come from either the two step compile or the compilation of jsps into temporary java code which then is fed to javac or jasper. Jesse Alexander (KBSA 21) wrote: > -----Original Message----- > I only can say if speed is an issue, either move away from WTP based > plugins or wait for better times. To split the project into several > smaller subprojects and have ant doing the merge probably is the way to > go currently. > > I cannot say how Nitrox behaves speedwise. > -----/Original Message----- > NitroX is no racecar. And I often have to use a "-clean" startup to > reset its internals... > > But, to do justice to all tools, so far I have done no project > of a similar size with Exadel or any of the other competitors. > > > > -----Original Message----- > As for Eclipse itself, Eclipse unless you run it on a Mac is fast, > memory is the keypoint, you should give Eclipse more ram that its > standard settings would give it (which are around 64MB) > > I usually start my Eclipses with following settings: > -vmargs -Xmx512m -Xms200m -XX:MaxPermSize=200m > -----/Original Message----- > Generally Java loves and eats memory. I have no Eclipse-setup with less > than > 768MB (both -Xmx and -Xms, I do not like the JVM to size up and shrink > its > memory footprint). > > regards > Alexander >
