/
pom.xml
186 lines (177 loc) · 6.48 KB
/
pom.xml
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
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
<?xml version="1.0" encoding="UTF-8" ?>
<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>bradleyross.pom-tutorials</groupId>
<artifactId>pom-tutorials-parent</artifactId>
<version>0.0.1-SNAPSHOT</version>
<packaging>pom</packaging>
<modules>
<module>tutorials-webapp1</module>
<module>tutorials-common</module>
<module>tutorials-launch</module>
<module>tutorials-log4j2</module>
<module>tutorials-log4j1</module>
<module>tutorials-development</module>
</modules>
<properties>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
</properties>
<!--
http://stackoverflow.com/questions/15886209/maven-is-not-working-in-java-8-when-javadoc-tags-are-incomplete
The Maven javadoc tool for Java 8 is very picky about correctly formed
HTML tags. This option turns off the checking for Java 8.
In creating a range of versions, a square bracket means inclusive while
a parenthesis means exclusive.
[1.8,) means every version from 1.8 onward
[1.8,1.9) means every version greater or equal to 1.8 and less than 1.9.
Since I finally resolved the HTML problems in the Javadocs, I commented out
the change.
The Javadoc plugin in Mavn has the following parameters related to
linking between Javadoc directories: destDir, detectJavaApiLink,
detectLinks, detectOfflineLinks.
It appears that most of the problems with the Maven Javadoc Plugin were
fixed by a later version of the JDK
-->
<profiles>
<profile>
<id>doclint-java8-disable</id>
<activation>
<jdk>[1.8,)</jdk>
</activation>
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-javadoc-plugin</artifactId>
<version>2.10.4</version>
<configuration>
<linksource>true</linksource>
<quiet>true</quiet>
<links>
<link>https://docs.oracle.com/javase/8/docs/api/</link>
<link>https://docs.oracle.com/javaee/6/api/</link>
<!-- http://www.slf4j.org/api/ -->
<link>http://www.jfree.org/jfreechart/api/javadoc/</link>
<link>http://www.jfree.org/jcommon/api/</link>
<link>http://jackcess.sourceforge.net/apidocs/</link>
<link>https://commons.apache.org/proper/commons-logging/apidocs/</link>
<link>https://logging.apache.org/log4j/2.x/log4j-api/apidocs/</link>
<link>http://logging.apache.org/log4j/2.x/log4j-1.2-api/apidocs/</link>
</links>
<offlineLinks>
<!-- This apparently means that package-list is in
the target/site/slf4j directory. It has to be in that directory for
each module.
For the slf4j Javadoc, the links work if I use offlineLink, but not if I use link.
When I did an internet search, it appeared that some web sites were not returning
files unless the HTTP headers contained an agent description. That could be the problem
in this case.
-->
<offlineLink>
<url>http://www.slf4j.org/api/</url>
<location>../slf4j</location>
</offlineLink>
</offlineLinks>
<!-- <additionalparam>-Xdoclint:none</additionalparam> -->
</configuration>
</plugin>
</plugins>
</build>
</profile>
<profile>
<id>prior versions</id>
<activation>
<jdk>(,1.7)</jdk>
</activation>
<build>
<!--
It appears that maven-javadoc-plugin:2.10.3 has a dependency on log4j-1.2.14
-->
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-javadoc-plugin</artifactId>
<version>2.10.4</version>
<configuration>
<linksource>true</linksource>
<quiet>true</quiet>
<links>
<link>https://docs.oracle.com/javase/8/docs/api/</link>
<link>https://docs.oracle.com/javaee/6/api/</link>
<!-- <link>http://www.slf4j.org/api/</link> -->
<link>http://www.jfree.org/jfreechart/api/javadoc/</link>
<link>http://www.jfree.org/jcommon/api/</link>
<link>http://jackcess.sourceforge.net/apidocs/</link>
<link>https://commons.apache.org/proper/commons-logging/apidocs/</link>
<link>https://logging.apache.org/log4j/2.x/log4j-api/apidocs/</link>
<link>http://logging.apache.org/log4j/2.x/log4j-1.2-api/apidocs/</link>
</links>
<offlineLinks>
<!-- This apparently means that package-list is in
the target/site/slf4j directory. It has to be in that directory for
each module.
-->
<offlineLink>
<url>http://www.slf4j.org/api/</url>
<location>../slf4j</location>
</offlineLink>
</offlineLinks>
</configuration>
</plugin>
</plugins>
</build>
</profile>
</profiles>
<!--
http://stackoverflow.com/questions/567996/can-maven-collect-all-the-dependent-jars-for-a-project-to-help-with-application
This option places copies of all of the jar files in the target directory.
-->
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-dependency-plugin</artifactId>
<version>2.10</version>
<configuration>
<quiet>true</quiet>
<outputDirectory>
${project.build.directory}/dependencies
</outputDirectory>
</configuration>
</plugin>
<plugin>
<!--
Some of the J2EE technologies require JRE 1.6
-->
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<version>3.5.1</version>
<configuration>
<source>1.8</source>
<target>1.8</target>
</configuration>
</plugin>
</plugins>
</build>
<!--
This dependency is required because the maven-javadoc-plugin:2.10.3 has
a dependency on maven-core:2.2.1, which has direct or indirect
dependencies on slf4j-nop:1.5.3 and slf4j-jdk14:1.5.6.
maven-core:2.2.1 : slf4j-jdk14:1.5.6
maven-core:2.2.1 : wagon-webdav-jackrabbit:1.0-beta-6 : slf4j-nop:1.5.3
These dependencies caused conflicts when dealing with various logging
schemes that used different jar files.
By inserting a dependency on maven-core:3.3.9, it forces the system
to use maven-core:3.3.9 instead of maven-core:2.2.1.
-->
<dependencies>
<dependency>
<groupId>org.apache.maven</groupId>
<artifactId>maven-core</artifactId>
<version>3.3.9</version>
</dependency>
</dependencies>
</project>