This suggests inefficiency in existing implementation. We use this model
internally with some custom optimizations for a very large codebase.
--
Regards,
Igor
On December 12, 2016 3:25:35 PM Christian Schulte <c...@schulte.it> wrote:
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: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
