-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathpom.xml
More file actions
96 lines (83 loc) · 3.2 KB
/
pom.xml
File metadata and controls
96 lines (83 loc) · 3.2 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>com.crotontech</groupId>
<artifactId>mavenprofiles</artifactId>
<version>0.0.1-SNAPSHOT</version>
<description>Maven deployment profile sample</description>
<build>
<filters>
<!-- Ensures that the *.properties file is always loaded from the
configuration directory of the active Maven profile. -->
<filter>profiles/${build.profile.id}/${build.profile.id}.properties</filter>
</filters>
<resources>
<!-- Placeholders that are found from the files located in the configured
resource directories are replaced with the property values found from the
profile specific configuration file. -->
<resource>
<filtering>true</filtering>
<directory>src/main/resources</directory>
</resource>
</resources>
</build>
<dependencies>
<dependency>
<groupId>log4j</groupId>
<artifactId>log4j</artifactId>
<version>1.2.17</version>
</dependency>
<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>4.11</version>
<scope>test</scope>
</dependency>
</dependencies>
<!-- Profile configuration -->
<profiles>
<!-- The configuration of the development profile -->
<profile>
<id>dev</id>
<!-- The development profile is active by default -->
<activation>
<activeByDefault>true</activeByDefault>
</activation>
<properties>
<!-- Specifies the build.profile.id property that must be equal than
the name of the directory that contains the profile specific configuration
file. Because the name of the directory that contains the configuration file
of the development profile is dev, we must set the value of the build.profile.id
property to dev. -->
<build.profile.id>dev</build.profile.id>
<!-- Only unit tests are run when the development profile is active -->
<skip.integration.tests>true</skip.integration.tests>
<skip.unit.tests>false</skip.unit.tests>
</properties>
</profile>
<!-- The configuration of the production profile -->
<profile>
<id>prod</id>
<properties>
<!-- Specifies the build.profile.id property that must be equal than
the name of the directory that contains the profile specific configuration
file. Because the name of the directory that contains the configuration file
of the production profile is prod, we must set the value of the build.profile.id
property to prod. -->
<build.profile.id>prod</build.profile.id>
</properties>
</profile>
<!-- The configuration of the testing profile -->
<profile>
<id>test</id>
<properties>
<!-- Specifies the build.profile.id property that must be equal than
the name of the directory that contains the profile specific configuration
file. Because the name of the directory that contains the configuration file
of the testing profile is test, we must set the value of the build.profile.id
property to test. -->
<build.profile.id>test</build.profile.id>
</properties>
</profile>
</profiles>
</project>