<mailto:
jpl@xxxxxxxxxxxxx>> wrote:
Hi,
As a new user of M2Eclipse, I am wondering about typical and minimal
build times. What I have here is a multi-module project structured
according to the usual recommendations (much like the multi-module
enterprise example in the Maven by Example book). Building it (from
non-dirty state) using M2Eclipse (or directly with Maven) takes
about 30 seconds. So after any slightest change in code I have to
wait for at least 30 seconds before seeing the effect of my change
in the browser. Given that Eclipse compiles the individual classes
instantly as I type, the build step seems like a great waste and an
unnecessary overhead.
What are your impressions? Does working with Maven necessarily
induce such delays into the edit-compile-run cycle and should one
treat this overhead as a price for having a portable build system
("just buy faster hardware")? Or are there any tried-and-true tricks
for speeding up the process? Right now I'm thinking about hacking
together something project-specific that detects changes in .class
files and then updates the corresponding resources in WEB-INF. But
that's very crude and essentially means working around Maven (in
development) instead of relying on it equally everywhere.
Regards,
Jan Ploski
______________________________
___________________
m2e-users mailing list