?? Windows has environment variables (My Computer | Properties) (e.g. JAVA_HOME); you just have to open a new terminal after changing them.

Environment variables are easier than system properties because they get propagated to the gradle worker task automatically.

I'd prefer to default to faster build to make the experience better for new developers - even 13 minutes is too long; we need to look at other candidates.

However, we should make a note in the developer guidelines that if you modify any affected module, you need to do the full build.

If there's a better way to do it using gradle, go ahead :smile: 

With Spring-AMQP, the maven build used to exclude the integration tests and they were only run on the nightly build; when @ghillert moved the build to gradle he did not find a way to selectively omit those tests AFAIK.