Weird behaviour with Spring config and Maven profiles - spring

Question

I have this weird behavior working with the Maven <filter> tag and Spring configs . My understanding is that a Spring config is a plain XML file to Maven but I'm encountering issues with the <context:component-scan base-package="com.xyz"/> tag . The test XML file is as below
<beans xmlns="http://www.springframework.org/schema/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:context="http://www.springframework.org/schema/context"
xmlns:aop="http://www.springframework.org/schema/aop"
xmlns:tx="http://www.springframework.org/schema/tx"
xmlns:jee="http://www.springframework.org/schema/jee"
xsi:schemaLocation="http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans-3.0.xsd
http://www.springframework.org/schema/context
http://www.springframework.org/schema/context/spring-context-3.0.xsd
http://www.springframework.org/schema/aop
http://www.springframework.org/schema/aop/spring-aop-3.0.xsd
http://www.springframework.org/schema/tx
http://www.springframework.org/schema/tx/spring-tx-3.0.xsd
http://www.springframework.org/schema/jee
http://www.springframework.org/schema/jee/spring-jee-3.0.xsd"
default-autowire="byName">
<!-- Import the DataSource configurations -->
<import resource="classpath:spring/MyDataSource.xml"/>
<!-- Property File location -->
<context:property-placeholder location="${ext.properties.dir}"/>
<!--The services are auto-detected POJOs labeled with the #Service annotation.-->
<context:component-scan base-package="com.xyz"/>
</beans>
and the Maven profiles configuration as below
<build>
.....
<resources>
<resource>
<directory>src/main/resources</directory>
<filtering>true</filtering>
</resource>
</resources>
<filters>
<filter>src/main/resources/build/build-${environment}.properties</filter>
</filters>
</build>
<profiles>
<profile>
<id>uat</id>
<activation>
<property>
<name>env</name>
<value>uat</value>
</property>
</activation>
<properties>
<environment>uat</environment>
</properties>
</profile>
<profile>
<id>prod</id>
<activation>
<property>
<name>env</name>
<value>prod</value>
</property>
<activeByDefault>true</activeByDefault>
</activation>
<properties>
<environment>prod</environment>
</properties>
</profile>
</profiles>
Contents of build-dev.properties are
ext.properties.dir=file:///C:/Temp/myProp.properties
My issue was that the Maven profile filtering was not working and the property ${ext.properties.dir} was not getting replaced during the packaging process . It stated working when I removed the <context:component-scan base-package="com.xyz"/> tag and hence I placed it below the property which needs to be filtered . Now everything works fine . My question is what's the issue with <context:component-scan base-package="com.xyz"/> ?

Answer 1

I do not think that <context:component-scan base-package="com.xyz"/> but the comment above
<!--The services are auto-detected POJOs labeled with the #Service annotation.-->
The # has a special meaning in maven fitlers.
To be honest I have the feeling that there are to many overlapping in syntax between spring configuration files and maven filters to use them together. My "solution" is to use (as long as possible) two files for the spring configuration.
a Property file, that is manipulated by spring filters
a normal Spring configuration file (with placeholders) that uses a PropertyPlaceholder Configurer to load the property file.