/
pom.xml
296 lines (256 loc) · 13.2 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
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
<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>
<parent>
<groupId>org.rcsb</groupId>
<artifactId>mmtf</artifactId>
<version>1.0.1-SNAPSHOT</version>
</parent>
<artifactId>mmtf-serialization</artifactId>
<packaging>jar</packaging>
<name>mmtf-serialization</name>
<url>http://maven.apache.org</url>
<properties>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
</properties>
<dependencies>
<dependency>
<groupId>org.msgpack</groupId>
<artifactId>jackson-dataformat-msgpack</artifactId>
<version>0.7.1</version>
</dependency>
<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
</dependency>
<dependency>
<groupId>uk.co.jemos.podam</groupId>
<artifactId>podam</artifactId>
</dependency>
<dependency>
<groupId>org.unitils</groupId>
<artifactId>unitils-core</artifactId>
</dependency>
<dependency>
<groupId>commons-beanutils</groupId>
<artifactId>commons-beanutils</artifactId>
</dependency>
</dependencies>
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jar-plugin</artifactId>
<configuration>
</configuration>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<configuration>
<debug>true</debug>
</configuration>
</plugin>
<plugin>
<groupId>pl.project13.maven</groupId>
<artifactId>git-commit-id-plugin</artifactId>
<version>2.2.0</version>
<executions>
<execution>
<goals>
<goal>revision</goal>
</goals>
</execution>
</executions>
<configuration>
<!-- If you'd like to tell the plugin where your .git directory is,
use this setting, otherwise we'll perform a search trying to figure out the
right directory. It's better to add it explicite IMHO. -->
<dotGitDirectory>${project.basedir}/.git</dotGitDirectory>
<!-- that's the default value, you don't have to set it -->
<prefix>git</prefix>
<!-- that's the default value -->
<dateFormat>dd.MM.yyyy '@' HH:mm:ss z</dateFormat>
<!-- @since 2.2.0 -->
<!-- If you want to set the timezone of the dateformat to anything in
particular you can do this by using this option. As a general warning try
to avoid three-letter time zone IDs because the same abbreviation are often
used for multiple time zones. The default value we'll use the timezone use
the timezone that's shipped with java (java.util.TimeZone.getDefault().getID()).
*Note*: If you plan to set the java's timezone by using `MAVEN_OPTS=-Duser.timezone=UTC
mvn clean package`, `mvn clean package -Duser.timezone=UTC` or any other
configuration keep in mind that this option will override those settings
and will not take other configurations into account! -->
<dateFormatTimeZone>${user.timezone}</dateFormatTimeZone>
<!-- false is default here, it prints some more information during the
build -->
<verbose>false</verbose>
<!-- ALTERNATE SETUP - GENERATE FILE -->
<!-- If you want to keep git information, even in your WAR file etc,
use this mode, which will generate a properties file (with filled out values)
which you can then normally read using new Properties().load(/**/) -->
<!-- this is false by default, forces the plugin to generate the git.properties
file -->
<generateGitPropertiesFile>true</generateGitPropertiesFile>
<!-- The path for the to be generated properties file, it's relative
to ${project.basedir} The default value is ${project.build.outputDirectory}/git.properties -->
<generateGitPropertiesFilename>${project.build.outputDirectory}/git.properties</generateGitPropertiesFilename>
<!-- Denotes the format to save properties in. Valid options are "properties"
(default) and "json". Properties will be saved to the generateGitPropertiesFilename
if generateGitPropertiesFile is set to `true`. -->
<format>properties</format>
<!-- this is true by default; You may want to set this to false, if
the plugin should run inside a <packaging>pom</packaging> project. Most projects
won't need to override this property. For an use-case for this kind of behaviour
see: https://github.com/ktoso/maven-git-commit-id-plugin/issues/21 -->
<skipPoms>true</skipPoms>
<!-- @since 2.1.4 -->
<!-- Tell maven-git-commit-id to inject the git properties into all
reactor projects not just the current one. For details about why you might
want to skip this, read this issue: https://github.com/ktoso/maven-git-commit-id-plugin/pull/65
The property is set to ``false`` by default to prevent the overriding of
properties that may be unrelated to the project. -->
<injectAllReactorProjects>false</injectAllReactorProjects>
<!-- @since 2.0.4 -->
<!-- true by default, controls whether the plugin will fail when no
.git directory is found, when set to false the plugin will just skip execution -->
<failOnNoGitDirectory>true</failOnNoGitDirectory>
<!-- @since 2.1.5 -->
<!-- true by default, controls whether the plugin will fail if it was
unable to obtain enough data for a complete run, if you don't care about
this, you may want to set this value to false. -->
<failOnUnableToExtractRepoInfo>true</failOnUnableToExtractRepoInfo>
<!-- @since 2.1.8 -->
<!-- skip the plugin execution completely. This is useful for e.g. profile
activated plugin invocations or to use properties to enable / disable pom
features. Default value is 'false'. -->
<skip>false</skip>
<!-- @since 2.1.12 -->
<!-- Use with caution! In a multi-module build, only run once. This
means that the plugins effects will only execute once, for the parent project.
This probably won't "do the right thing" if your project has more than one
git repository. Important: If you're using `generateGitPropertiesFile`, setting
`runOnlyOnce` will make the plugin only generate the file in the directory
where you started your build (!). The `git.*` maven properties are available
in all modules. Default value is `false`. -->
<runOnlyOnce>false</runOnlyOnce>
<!-- @since 2.1.9 -->
<!-- Can be used to exclude certain properties from being emited into
the resulting file. May be useful when you want to hide {@code git.remote.origin.url}
(maybe because it contains your repo password?), or the email of the committer
etc. Each value may be globbing, that is, you can write {@code git.commit.user.*}
to exclude both, the {@code name}, as well as {@code email} properties from
being emitted into the resulting files. Please note that the strings here
are Java regexes ({@code .*} is globbing, not plain {@code *}). -->
<excludeProperties>
<!-- <excludeProperty>git.user.*</excludeProperty> -->
</excludeProperties>
<!-- @since 2.1.14 -->
<!-- Can be used to include only certain properties into the resulting
file. Will be overruled by the exclude properties. Each value may be globbing,
that is, you can write {@code git.commit.user.*} to include both, the {@code
name}, as well as {@code email} properties into the resulting files. Please
note that the strings here are Java regexes ({@code .*} is globbing, not
plain {@code *}). -->
<includeOnlyProperties>
<!-- <includeOnlyProperty>^git.commit.id.full$</includeOnlyProperty> -->
</includeOnlyProperties>
<!-- @since 2.1.10 -->
<!-- false is default here, if set to true it uses native `git` excutable
for extracting all data. This usually has better performance than the default
(jgit) implemenation, but requires you to have git available as executable
for the build as well as *might break unexpectedly* when you upgrade your
system-wide git installation. As rule of thumb - stay on `jgit` (keep this
`false`) until you notice performance problems. -->
<useNativeGit>false</useNativeGit>
<!-- @since v2.0.4 -->
<!-- Controls the length of the abbreviated git commit it (git.commit.id.abbrev)
Defaults to `7`. `0` carries the special meaning. Maximum value is `40`,
because of max SHA-1 length. -->
<abbrevLength>7</abbrevLength>
<!-- @since v2.2.0 -->
<!-- The option can be used to tell the plugin how it should generate
the 'git.commit.id' property. Due to some naming issues when exporting the
properties as an json-object (https://github.com/ktoso/maven-git-commit-id-plugin/issues/122)
we needed to make it possible to export all properties as a valid json-object.
Due to the fact that this is one of the major properties the plugin is exporting
we just don't want to change the exporting mechanism and somehow throw the
backwards compatibility away. We rather provide a convient switch where you
can choose if you would like the properties as they always had been, or if
you rather need to support full json-object compatibility. In the case you
need to fully support json-object we unfortunately need to change the 'git.commit.id'
property from 'git.commit.id' to 'git.commit.id.full' in the exporting mechanism
to allow the generation of a fully valid json object. Currently the switch
allows two different options: 1. By default this property is set to 'flat'
and will generate the formerly known property 'git.commit.id' as it was in
the previous versions of the plugin. Keeping it to 'flat' by default preserve
backwards compatibility and does not require further adjustments by the end
user. 2. If you set this switch to 'full' the plugin will export the formerly
known property 'git.commit.id' as 'git.commit.id.full' and therefore will
generate a fully valid json object in the exporting mechanism. *Note*: Depending
on your plugin configuration you obviously can choose the 'prefix' of your
properties by setting it accordingly in the plugin's configuration. As a
result this is therefore only an illustration what the switch means when
the 'prefix' is set to it's default value. *Note*: If you set the value to
something that's not equal to 'flat' or 'full' (ignoring the case) the plugin
will output a warning and will fallback to the default 'flat' mode. -->
<commitIdGenerationMode>flat</commitIdGenerationMode>
<!-- @since 2.1.0 -->
<!-- read up about git-describe on the in man, or it's homepage - it's
a really powerful versioning helper and the recommended way to use git-commit-id-plugin.
The configuration bellow is optional, by default describe will run "just
like git-describe on the command line", even though it's a JGit reimplementation. -->
<gitDescribe>
<!-- don't generate the describe property -->
<skip>false</skip>
<!-- if no tag was found "near" this commit, just print the commit's
id instead, helpful when you always expect this field to be not-empty -->
<always>false</always>
<!-- how many chars should be displayed as the commit object id? 7
is git's default, 0 has a special meaning (see end of this README.md), and
40 is the maximum value here -->
<abbrev>7</abbrev>
<!-- when the build is triggered while the repo is in "dirty state",
append this suffix -->
<dirty>-dirty</dirty>
<!-- Only consider tags matching the given pattern. This can be used
to avoid leaking private tags from the repository. -->
<match>*</match>
<!-- always print using the "tag-commits_from_tag-g_commit_id-maybe_dirty"
format, even if "on" a tag. The distance will always be 0 if you're "on"
the tag. -->
<forceLongFormat>false</forceLongFormat>
</gitDescribe>
<!-- this is false by default, forces the plugin to generate the git.properties
file -->
<generateGitPropertiesFile>true</generateGitPropertiesFile>
<!-- The path for the properties file to be generated. See Super Pom
for default variable reference https://maven.apache.org/guides/introduction/introduction-to-the-pom.html -->
<generateGitPropertiesFilename>${project.build.outputDirectory}/git.properties</generateGitPropertiesFilename>
</configuration>
</plugin>
<!-- END OF GIT COMMIT ID PLUGIN CONFIGURATION -->
<!-- other plugins -->
</plugins>
</build>
<reporting>
<plugins>
<plugin>
<artifactId>maven-javadoc-plugin</artifactId>
<version>2.10.1</version>
<configuration>
<aggregate>true</aggregate>
<breakiterator>true</breakiterator>
<quiet>true</quiet>
<source>1.8</source>
<verbose>false</verbose>
<linksource>true</linksource>
</configuration>
</plugin>
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>findbugs-maven-plugin</artifactId>
<version>3.0.3</version>
</plugin>
</plugins>
</reporting>
</project>