Resolving ${} system properties in @PropertySource annotation does not work anymore [SPR-9380]

[spring-projects-issues]

Marcel Overdijk opened SPR-9380 and commented

I have the blow AppConfig class in my project:

@Configuration
@ComponentScan(basePackages = { "my.project" })
@PropertySource({ "classpath:/META-INF/config.properties", "classpath:/META-INF/config-${my.runtime.environment}.properties" })
public class AppConfig {

	private static Log LOG = LogFactory.getLog(AppConfig.class);

	@Bean
	public static PropertySourcesPlaceholderConfigurer propertySourcesPlaceholderConfigurer() {
		return new PropertySourcesPlaceholderConfigurer();
	}

Resolving the ${my.runtime.environment} in the @PropertySource does not work anymore in Spring 3.1.1 while I was just upgrading from 3.1.0.
The same code works fine in 3.1.0 but gives this error in 3.1.1:

Failed to load bean class: mt.project.config.AppConfig; nested exception is java.io.FileNotFoundException: class path resource [META-INF/config-${my.runtime.environment}.properties] cannot be opened because it does not exist

The config file exists and the system property is set (I logged that as well), and just to mention it again. In 3.1.0 this works fine.

---

Affects: 3.1.1

Issue Links:

• Fix regression in @PropertySource placeholder resolution [SPR-9133] #13772 Fix regression in @PropertySource placeholder resolution ("duplicates")
• @PropertySource annotation with multiple values and a name fails to register all property sources [SPR-9127] #13766 @PropertySource annotation with multiple values and a name fails to register all property sources ("duplicates")

[spring-projects-issues]

Chris Beams commented

Hi Marcel,

Sorry for the inconvenience with this issue. It was originally reported and fixed against 3.2.x in #13772, and backported to 3.1.x with #13766.

The fix unfortunately came just after the release of 3.1.1, but you can find it in 3.1.2.BUILD-SNAPSHOT.