There is no longer a reserved default profile named 'default'. Rather,
users must explicitly specify a default profile or profiles via
ConfigurableEnvironment.setDefaultProfiles(String...)
- or -
spring.profile.default="pD1,pD2"
Per above, the setDefaultProfile(String) method now accepts a variable
number of profile names (one or more). This is symmetrical with the
existing setActiveProfiles(String...) method.
A typical scenario might involve setting both a default profile as a
servlet context property in web.xml and then setting an active profile
when deploying to production.
git-svn-id: https://src.springframework.org/svn/spring-framework/trunk@3809 50f2f4bb-b051-0410-bef5-90022cba6387
@ -59,6 +58,7 @@ public class ClassPathScanningCandidateComponentProviderTests {
@@ -59,6 +58,7 @@ public class ClassPathScanningCandidateComponentProviderTests {
@ -219,6 +219,7 @@ public class ClassPathScanningCandidateComponentProviderTests {
@@ -219,6 +219,7 @@ public class ClassPathScanningCandidateComponentProviderTests {
@ -231,6 +232,7 @@ public class ClassPathScanningCandidateComponentProviderTests {
@@ -231,6 +232,7 @@ public class ClassPathScanningCandidateComponentProviderTests {
@ -238,6 +240,7 @@ public class ClassPathScanningCandidateComponentProviderTests {
@@ -238,6 +240,7 @@ public class ClassPathScanningCandidateComponentProviderTests {
@ -245,6 +248,7 @@ public class ClassPathScanningCandidateComponentProviderTests {
@@ -245,6 +248,7 @@ public class ClassPathScanningCandidateComponentProviderTests {
@ -263,13 +267,13 @@ public class ClassPathScanningCandidateComponentProviderTests {
@@ -263,13 +267,13 @@ public class ClassPathScanningCandidateComponentProviderTests {