On Tue, Jun 29, 2010 at 8:58 PM, Tor Norbye <[email protected]> wrote:
> Sorry, I don't use Maven so I can't really comment on this other than > to say I'm sorry it sounds like it's not fixed yet. > > I suspect the Maven support itself may be initiating a lot of scanning > or refresh operations, since Maven is an external tool, so after it > runs the IDE has really very little idea what running the task has > done. I used to work on something similar, the Rails support in > NetBeans, and when running certain code generators via the rails > infrastructure I had no idea what would happen to the files on disk, > so to be on the safe side, for any unknown actions it would just force > a disk refresh. It's possible that the Maven support is doing > something similar -- I'm just speculating here. All I can say is that > for the project types I'm using (Java+JavaFX) and for some other > project types I've seen described (such as PHP) it is working well. > One of the big pushes for maven 3 has been a better support layer for IDEs to build on. Recent versions of m2eclipse do a *lot* less work because the maven embedder component provides better integration. I've no idea about when NetBeans integration will start to use this (or even if it does already). -Dom -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
