Hi Dobes, You are right that if you wait for a built, your edit/compile/debug cycle will be very slow. I've found the answer is: don't wait for the build. Build once in Maven (without unit tests), then let your IDE build the needed files from there until you change branches.
If you have a unit test, even one that does nothing other than start the server, you can let your IDE maintain the working build. This even works with starting the Drillbit directly [1] (might be bit old). For example, a typical fix for me is: change a file, run a unit test, get feedback in 15 seconds or less. Thanks, - Paul [1] https://github.com/paul-rogers/drill/wiki/Launch-a-Drillbit-From-Eclipse On Tuesday, February 25, 2020, 10:53:28 AM PST, Dobes Vandermeer <[email protected]> wrote: Hi, I've been experimenting with some improvements to the drill Web UI & REST API but I find that I spend a lot of time waiting for the maven builds. It takes about 2.5 minutes for me to run maven install in order to test a change. I notice a lot of that is spent in building things that I haven't changed. However, I seem to lack the maven expertise to know the simplest way to tell it which packages to rebuild (or not). Do any of you who work regularly on the project have tips and tricks for reducing build times?
