On Dec 3, 2007 10:24 AM, Saloucious <[EMAIL PROTECTED]> wrote: > But it's not able to see affected files from modules which depend on > modified one, as Eclipse do.
Eclipse gets this by scanning the java files to identify dependencies (for code complete, etc) and when it does it's background compilation. Essentially, Eclipse has done a lot of work in the background and built a dependency tree for each class. It would most likely take Maven just as long to figure out the dependencies as to do a clean compile unless maven were to persist the results of a dependency analysis into the target folder... Of course that would make the normal compiles slower... If you are running a CI server in the background (http://hudson.dev.java.net/ anyone?) then the compile time is less of an issue for Maven builds. If you are looking to take the changes quickly while developing, your IDE will have recompiled the necessary files anyway, so what is the problem with Maven's method of compiling only newer .java files... there should be none of them as your IDE will have compiled them, all you are using Maven for in that case is the packaging of artifacts (which your IDE will do for you anyway... and you're only doing a Maven build as a pre-test to commiting your changes... oh so in that case you _should_ be doing a clean install not an incremental) Just my €0.02 -Stephen --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
