Disable DevTools' environment post-processors and auto-configuration when running tests

[wilkinsona]

Currently, when spring-boot-devtools is being used, it's on the classpath when a project's tests are being run using Maven or Gradle. If possible, we should exclude Dev Tools from the classpath so that the tests are run using a classpath that's as close to the application's runtime classpath as possible.

A few concerns:

• Eclipse makes no distinction between compile and test classpaths. If we do this the tests will run with different class paths in the IDE and on the command line.
• I'm not sure it's possible in Maven. @snicoll?

[snicoll]

Not possible in Maven AFAIK. The closest would be a (maven) profile that's only enabled when you run your app

[snicoll]

At this point, disabling devtools when it's running in a test environment would be the easiest. Thoughts @philwebb ?

[philwebb]

Let's try and do this in the code since Eclipse and Maven will require that solution anyway.

[snicoll]

And IntelliJ IDEA and Netbeans.

[philwebb]

@wilkinsona Is this specifically related to the restarer or is there some other problem? I'm just wondering what problems are being caused and where we need additional checks?

[wilkinsona]

It wasn't specific to the restarter. My goal was to run the tests with a classpath and behaviour that's as close as possible to how it will be once deployed. I haven't seen any specific problems.