All of these task should only happen when you open a new project. Otherwise all of it should be cached in the local repo.
When all of it is local it should NOT take so long. At least it doesnt in M2e. If you resort to a hack like opening only part of the reactor you should not be surprised if working on it is only semi-optimal. Manfred Christian Schulte wrote on 2016-12-12 15:25: > Am 12/12/16 um 23:23 schrieb Igor Fedorenko: >> Disagree. I think in most if not all cases we build entire project, not >> just random part of a project. > > Try opening a big multi-module project in Netbeans, for example. > Something like an J2EE application server. You can take a long walk > until it finishes downloading sources, javadoc, dependencies and the > background scanning task before you can change a single line of code. > Working on projects like that, I really only open the module(s) I need > to work on, build them in isolation and copy resuling jar files around - > during development. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
