Why does NetBeans always want to run a priming build in my Maven project?

Question

He often asks me how to do a priming assembly. At least every time it opens, for example. This is in NetBeans 7.1; version 6 did not do this.

I don’t even understand what he is doing. Googling points to http://wiki.netbeans.org/NewAndNoteworthyNB71#Maven , which states that this is a replacement for "rebooting online," which is also a mystery to me. But the brief paragraph mentions that it is intended to sort the missing artifacts.

But do you need to work so often? This project has many modules; Could there be a dependency problem NetBeans is trying to figure out?

Answer 1

I believe that Netbeans can decide which dependencies it should compile for your project (maybe it can highlight errors in the editor / navigator).

As for why he now does this every time you open a project, I don’t know. I suspect that previous versions did this automatically, and this change is intended for users with huge projects who might not want to wait, and instead let them choose which modules they want to destroy the stuffing.

It would be nice if the option turned off, though.

Answer 2

This happens anytime you open a new project, especially one that was created from existing sources, since Maven needs to work with dependencies and load them into its local cache.

The advantage here is that any missing dependencies, such as parent POMs, are detected immediately.

Answer 3

This is a constant problem for me. It starts building when I open Netbeans (7.3), which I can accept. Get your building and leave, please.

But then several times a day, when I notice that my car is becoming sluggish, I watch, and a rough “priming assembly” appears again.

Why do you need to do this? My addictions have not changed.