I feel that in general having an huge monolithic project is kind of a project-smell. Btw I have some big project with 100+ modules so I can see your pain. In the daywork experience a single developer doesn't work on all of the modules but usually you touch 1-2 modules and maybe some integration/system test. If you need to rebuild the full project for every change maybe there is something wrong with the overall design.
I think you have you motivations for your layout, so let's talk about your proposal. If you have a way to split your project in subsystems you can use some shared remote repository for deploying snapshots in order to share intermediate results with other developers If your goal is to be ready for releases I don't get your point. Usually you work with snapshots and for a release you have to rebuild one time and only once the full codebase in order to ensure that you a consistent build of the project. With all of this kind of temporary caches how do you ensure that the final artifacts are the intended ones? Beside note: this is not a real VOTE thread Just my 2 cents don't get me wrong, I admire your will to improve Maven ecosystem with this cool feature! Thank you for contribution your work. We will try to get the best Enrico Il sab 14 set 2019, 08:29 Laird Nelson <ljnel...@gmail.com> ha scritto: > On Fri, Sep 13, 2019 at 11:01 PM Alexander Ashitkin < > alexander.ashit...@db.com> wrote: > > > This feature is true incremental build – you don’t build modules which > > were not changed at all and build only modified/changed ones. > > > > Suppose module B depends on module A and I change A. Does B get rebuilt in > your system? > > Best, > Laird >
