It should be easier to set which profile is active when running `gradle` tasks

[berlin-ab]

When I run:

$ gradle bootRun -Pspring.profiles.active=dev

or

$ gradle bootRun -Dspring.profiles.active=dev

... my application does not start in the dev @Profile, and it should.

Here's my example project:

https://github.com/berlin-ab/springbootblog/tree/blog/profiles

[berlin-ab]

It works after following the advice here: #592

Although, I think there should be a change made to the gradle plugin to make this the default. We want to be able to run specify that gradle should use the test profile, and we want to do that often.

[dsyer]

When you say "make this the default" what exactly does that mean? Does it amount to setting run { systemProperties = System.properties } in the plugin (instead of requiring you to do it in "build.gradle"? Or do you want to create a project template for your work that has that set already (along the lines of some of your other queries), and we could do that outside Boot?

[berlin-ab]

@dsyer I was intentionally leaving the solution up to you by being vague, but now that you ask... I'd put the configuration in the spring boot gradle plugin, so it is not something that the developer needs to think about.

[dougio]

I set spring profile in a shell variable as was mentioned here, this is simple enough for me.

SPRING_PROFILES_ACTIVE=dev gradle clean bootRun

[JamesMcMahon]

While the shell variable solution is great it still feels like this something missing from Spring boot, especially given it's close parity with Rails.

[jklap]

Would be nice if you could set the profile in build.gradle cleanly such as

bootRun {
  profile: development
}

Seems like the best suggestion from #592 is:

bootRun {
  environment SPRING_PROFILES_ACTIVE: environment.SPRING_PROFILES_ACTIVE ?: "local"
}

[vjm]

adding bootRun.systemProperties = System.properties to your gradle will respect gradle bootRun -Dspring.profiles.active=dev.

[wilkinsona]

#1176 will address this