Use of profile in Maven2

One of the benefits of using MAVEN to manage your project is that you can use different compilation packaging settings for different environments to facilitate a multi-environment package deployment, generally we have at least two development environment and formal environment for the development project, the configuration information for both environments will be different, such as database configuration. We can use MAVEN's profile definition to differentiate, for example, we define the following fragment in the project's Pom file:

2. <project>

4. <modelversion>4.0.0</modelversion>

6. <groupid>cc.mzone</groupid>

8. <artifactid>myjar</artifactid>

10. <version>0.1</version>

12. <packaging>jar</packaging>

14. <build>

16. <resources>

18. <resource>

20. <directory>src/main/resources</directory>

22. <includes>

24. <include>* *</include>

26. </includes>

28. <filtering>true</filtering>

30. </resource>

32. </resources>

34. </build>

38. <properties>

40. <jdbc.url>jdbc:mysql://localhost:3306/abc</jdbc.url>

42. <jdbc.username>root</jdbc.username>

44. <jdbc.password>root</jdbc.password>

46. </properties>

50. <profiles>

52. <profile>

54. <id>product</id>

56. <properties>

58. <jdbc.url>jdbc:mysql://localhost:3306/abc123</jdbc.url>

60. <jdbc.username>rootuser</jdbc.username>

62. <jdbc.password>rootpwd</jdbc.password>

64. </properties>

66. </profile>

68. </profiles>

70. </project>

Here we define the relevant configuration of the database in the Pom file, define a profile with the ID of product, and also define the relevant configuration of the database in this profile. This allows us to use the default JDBC setting when we use the mvn Package Command When we use mvn package-p product When Maven automatically uses the database configuration in profile with ID product, this is the overwrite of Maven read property profiles.

Then look at the configuration of the Resources section in the Pom file:

2. <resources>

4. <resource>

6. <directory>src/main/resources</directory>

8. <includes>

10. <include>* *</include>

12. </includes>

14. <filtering>true</filtering>

16. </resource>

18. </resources>

One of the most important is the <filtering>true</filtering> section, this configuration means filtering the placeholders in the specified properties file above, the placeholder is the form of the ${variable name} , Maven automatically reads the configuration file and then resolves the placeholder, replacing it with the attributes defined in the Pom file above. We can define a jdbc.properties configuration file under Src/main/resources, with the following content:

1. Jdbc.driver=com.mysql.jdbc.driver

2. Jdbc.url=${jdbc.url}

3. Jdbc.username=${jdbc.username}

4. jdbc.password=${jdbc.password}

The following effects are performed:

1. # # Use the default configuration information

2. MVN Clean Package

4. # # configuration information using the product environment

5. MVN Clean Package -P product

After executing the above command in two times, and then looking at the packaged results under the target directory of the project, you can see that the contents of the Jdbc.properties file vary with the parameters of the package, thus enabling our multi-environment configuration to be packaged automatically.

Use of profile in Maven2