This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Current Maven Dependency Download Strategies consist of: * Never * First Project Open Only * Every Project Open It will be very usable if we can add option like "Every change in POM", so all artifacts binaries/javadoc/sources can be automatically downloaded every time there is a change in POM...
Agreed. I would actually prefer to switch the default to "Every Project Open" (or your proposed option such as "Every Project Change"), since I think the performance issues can be overcome, and it is certainly more convenient to have everything downloaded for you. The main issue is that if the download from the IDE hangs, e.g. due to a transient network issue, it is very difficult to kill it cleanly - java.net.HttpURLConnection (used by the default "lightweight" HTTP wagon) does not seem to respond to Thread.interrupt, or anything else short of Thread.stop, contrary to what the Javadoc of InterruptedIOException might lead you to believe. Getting dependencies from a regular forked build is more robust since the Stop button just kills the process and any open sockets with it. (For this reason NB 7.1 no longer has the "reloading online" feature, but just prompts you to run an external build when one is needed to obtain critical artifacts such as a parent POM.)
So if I get it right, there will not be anything like this in NetBeans 7.1?
Definitely not; 7.1 feature freeze was on Monday. It may make it into a subsequent release if I can find time to work on it, though there are hundreds of competing open issues.
open question is how to define pom change though. When we get the event that the pom file was modified, or when the user or the codebase refreshes the project? Eg. the project can be change even by a change in settings file (different mirror or added repository, different profile) or the parent pom as well. Automated project refreshes could be too frequent though, maybe just the manually triggered ones? doesn't fully match the "on project change" description though..
The rationale behind it was to automatically get the artifacts when POM file was changed. I don't really thought about any other changes, that time... I think that changes in settings.xml, pom.xml + possible parents should trigger possible downloading of artifacts. Nothing else.
This old bug may not be relevant anymore. If you can still reproduce it in 8.2 development builds please reopen this issue. Thanks for your cooperation, NetBeans IDE 8.2 Release Boss