在這篇文章中 maven配置多個.properties文件,我們利用maven實現了不同環境使用不同的properties文件,但是有時候properties文件並不太適合一些對象性配置,這時候不得不使用yaml文件,那麼問題了,不同的環境怎麼使用不同的yaml文件呢?
最簡單的思路就是使用maven-resource-plugin,根據環境變量將文件拷貝到resource下面即可:
<plugin>
<artifactId>maven-resources-plugin</artifactId>
<executions>
<execution>
<id>dev</id>
<phase>validate</phase>
<goals>
<goal>copy-resources</goal>
</goals>
<configuration>
<outputDirectory>src/main/resources</outputDirectory>
<resources>
<resource>
<directory>src/main/env/dev/yaml</directory>
<filtering>true</filtering>
</resource>
</resources>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
完整的配置文件如下:
<profiles>
<!-- 開發環境,默認爲開發環境 -->
<profile>
<id>dev</id>
<build>
<filters>
<filter>
src/main/env/dev/biz.properties
</filter>
</filters>
<resources>
<resource>
<directory>src/main/resources</directory>
<filtering>true</filtering>
</resource>
</resources>
<plugins>
<plugin>
<artifactId>maven-resources-plugin</artifactId>
<executions>
<execution>
<id>dev</id>
<phase>validate</phase>
<goals>
<goal>copy-resources</goal>
</goals>
<configuration>
<outputDirectory>src/main/resources</outputDirectory>
<resources>
<resource>
<directory>src/main/env/dev/yaml</directory>
<filtering>true</filtering>
</resource>
</resources>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
<activation>
<activeByDefault>true</activeByDefault>
<property>
<name>dev</name>
</property>
</activation>
</profile>
<profile>
<id>testing</id>
<build>
<filters>
<filter>
src/main/env/testing/biz.properties
</filter>
</filters>
<resources>
<resource>
<directory>src/main/resources</directory>
<filtering>true</filtering>
</resource>
</resources>
<plugins>
<plugin>
<artifactId>maven-resources-plugin</artifactId>
<executions>
<execution>
<id>testing</id>
<phase>validate</phase>
<goals>
<goal>copy-resources</goal>
</goals>
<configuration>
<outputDirectory>src/main/resources</outputDirectory>
<resources>
<resource>
<directory>src/main/env/testing/yaml</directory>
<filtering>true</filtering>
</resource>
</resources>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
</profile>
</profiles>