I was experimenting with Netbeans 6.8 (I'm currently an Eclipse user) because I like having a profiler built into the IDE. It seems that for maven projects, netbeans does a full compile (it invokes process-classes) every time I try to run the project, as opposed to Eclipse, which uses the incremental Java compiler. Is there a way to avoid having netbeans run mvn process-classes every time I want to run the main class?
thanks, Jeff
As I wrote in a comment to the question, there is nothing bound to process-classes by default so the question is: what is currently occurring during this phase?
It could be indeed something related to profiling (to instrument the code). In that case, see if deactivating the profiling solves the problem.
It could also be somehow related to the Groovy support. I can't test this right now but when I look at this thread, I see that the exec-maven-plugin is called during process-classes. But I have no idea if this is done by NetBeans or if the POM contains stuff causing this (and the thread is almost one year old so things might have changed).
Could you post Maven's output?