Open mvitz opened 6 years ago
Probably the easiest option would be to change DevToolsPropertyDefaultsPostProcessor
to look for properties files on the classpath named in a certain way. We could then move the hard-coded ones we have into an actual properties file.
I was more thinking of a way to load an EnvironmentPostProcessor
in a specific way. Right now, this post-processor kicks in because it simply is in the library but perhaps we should generalize that a bit.
My first idea was providing a properties file to add some properties, too. But feel free (of course) to find a better solution that you are willing to support and maintain.
A colleague of mine wrote a custom spring boot starter (https://github.com/faucet-pipeline/faucet-pipeline-spring-boot-starter). This starter contains a property
faucet-pipeline.cache-manifest
which by default is set totrue
.However for development it's recommended setting this to
false
. This is described in the projects Readme but can easily be overseen. It forces any user of the starter to find a solution for setting this value to a different value in development as well.It would be nice if the starter could provide something that will be picked up by DevTools and configure this automatically.
I'm sure that this is useful for many other starters as well.