-Dspring.profiles.active ignored when mvn spring-boot:run

[kryger]

Upgrading 1.0.2.RELEASE->1.1.0.RELEASE changed how passing profile to mvn spring-boot:run works, the -Dspring.profiles.active flag seems to be ignored. I created a simple project that reproduces the problem: https://github.com/kryger/bug-spring-maven-profiles

(Note that application.yml defines port=3333, application-production.yml defines port=1111)

Steps to reproduce:

1. Check out the project - it uses 1.1.0.RELEASE
2. mvn spring-boot:run -Dspring.profiles.active=production -> Tomcat starts on port 3333 (expected 1111)
3. Edit pom.xml and change <version> to 1.0.2.RELEASE
4. mvn spring-boot:run -Dspring.profiles.active=production again -> Tomcat starts on port 1111

I had a look at 1.1.0.RELEASE's release notes but couldn't find anything that would explain this change - no idea if it's a bug or a feature :).

[snicoll]

In 1.1.0 the plugin forks a process which is the reason why your system property is no longer available. The release notes indicate that the documentation of the maven plugin are now published.

You'll find an example there

[kryger]

Ah, thanks - I'll have a look and close the issue as soon as I confirm it works.

[snicoll]

Cheers.

[kryger]

(For reference) The command should be:

mvn spring-boot:run -Drun.jvmArguments="-Dspring.profiles.active=production"

[snicoll]

I have also added a section in the release notes regarding this change. Thanks for the report!

[lacivert]

@kryger I tried your way but I could not succeed. spring.profiles.active is not a maven/pom parameter. I think there must be another way to go on command line. Are you sure that it works? I think this issue should be opened.

By the way I am working with spring boot 1.2.5 release, maven 3, java 8u60

[lacivert]

Sorry for misunderstanding, my fault! It was about another thing but this one works:

mvn spring-boot:run -Dspring.profiles.active="production"

[gregturn]

I have always liked "SPRING_PROFILES_ACTIVE=production mvn spring-boot:run". It's the way to pass lots of critical env variables to really any app, maven or whatever.

[clevertension]

@gregturn
you method is work, thanks