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
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
|
# How to use jdeb with Maven
Generating a default Debian package with maven is particular easy. Just add
the plugin to your POM like this
```xml
<build>
<plugins>
<plugin>
<artifactId>jdeb</artifactId>
<groupId>org.vafer</groupId>
<version>1.8</version>
<executions>
<execution>
<phase>package</phase>
<goals>
<goal>jdeb</goal>
</goals>
<configuration>
<dataSet>
<data>
<src>${project.build.directory}/${project.build.finalName}.jar</src>
<type>file</type>
<mapper>
<type>perm</type>
<prefix>/usr/share/jdeb/lib</prefix>
</mapper>
</data>
</dataSet>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
```
Or if you want to build a custom deb file
```xml
<!-- Indicate it's a deb package which will automatically execute jdeb goal -->
<packaging>deb</packaging>
<build>
<extensions>
<!-- Add support for the "deb" packaging -->
<extension>
<groupId>org.vafer</groupId>
<artifactId>jdeb</artifactId>
<version>1.8</version>
</extension>
</extensions>
<pluginManagement>
<plugins>
<plugin>
<artifactId>jdeb</artifactId>
<groupId>org.vafer</groupId>
<!-- Customize deb package -->
<configuration>
<dataSet>
<data>
<src>${project.build.directory}/preparedfiles</src>
<type>directory</type>
<mapper>
<type>perm</type>
<prefix>/usr/lib/xwiki/myproject</prefix>
</mapper>
</data>
</dataSet>
</configuration>
</plugin>
</plugins>
</pluginManagement>
</build>
```
At least the one main control file is required to control the creation of the
debian package. This required control file should be found in the control
directory (inside the data dir). By default the control file name is also `control` which gives a path of `src/deb/control/control` by default. This control file contains the metadata about the Debian package. Usually it will look something along the lines of
Package: [[name]]
Version: [[version]]
Section: misc
Priority: optional
Architecture: all
Depends: jdk (>= 1.5)
Maintainer: Torsten Curdt <torsten@something.com>
Description: jetty java servlet container
Distribution: development
Depends: default-jre | java6-runtime
but check out the [example](https://github.com/tcurdt/jdeb/tree/master/src/examples/maven) to get a better overview.
If the environment variables `DEBEMAIL` and `DEBFULLNAME` are both set this
will overrule the `Maintainer` field set in there. The `Installed-Size` will
also be injected. If a changes file is used, the `Distribution` usually comes
from that file. The default changes file is called `CHANGES.txt`. See below
for the syntax of the content of the changes file.
Property replacement will also occur in any of the standard debian control
files: conffiles, preinst, postinst, prerm, postrm. This allows dynamic
configuration of the form:
/etc/[[artifactId]]/[[artifactId]].properties
/etc/[[artifactId]]/log4j.xml
If you now do a `mvn clean install`, the `deb` goal will be called and
artifacts consisting of the deb and potentially the changes file will
automatically be attached to the project.
The jdeb maven plugin also supports a variety of configuration options. These
configuration options provide the same features available in the jdeb ant
task. To configure the jdeb maven plugin, populate the jdeb configuration
section with any of the following options:
Element | Description | Required
---------------- | ------------------------------------------------------------------------------------------ | -----------------------------------------------------------------
deb | The debian package to be generated | No; defaults to `${buildDirectory}/${artifactId}_${version}_all.deb`
type | Artifact type | No; defaults to `deb`
classifier | Artifact classifier | No; defaults to ''
controlDir | The directory containing the control files | No; defaults to `src/deb/control`
installDir | The default directory for the project artifact if no data section is present | No; defaults to `/opt/${artifactId}`
dataSet | A list of directories, tarballs, or files to include in the deb package | No; defaults to include your maven artifact
changesIn | The changes to add | No
changesOut | The changes file generated | No
changesSave | (NYI) The merged changes file | No
compression | (NYI) Compression method for the data file (`gzip`, `bzip2`, `xz` or `none`) | No; defaults to `gzip`
signPackage | If the debian package should be signed | No
signMethod | Which utility is used for verification (`dpkg-sig`, `debsig-verify`) | No; defaults to `debsig-verify`
signRole | Determines the filename of the signature, debsig only verifies `origin` | No; defaults to `origin`
signCfgPrefix | Prefix for when reading keyring, key and passphrase from settings.xml | No; defaults to `jdeb.`
keyring | The file containing the PGP keys | No
key | The name of the key to be used in the keyring | No
passphrase | The passphrase to use the key | No
attach | Attach artifact to project | No; defaults to `true`
snapshotExpand | Expand SNAPSHOT into the content of an environment variable or timestamp. | No; defaults to `false`
snapshotEnv | Name of the environment variable. If it's empty defaults to a timestamp. | No; defaults to `SNAPSHOT`
snapshotTemplate | Template for replacing the SNAPSHOT value. A timestamp format can be provided in brackets. | No;
verbose | Verbose logging | No; defaults to `true`, will be `false` in the future
skip | Indicates if an execution should be skipped | No; defaults to `false`
skipSubmodules | Skip goal on all submodules | No; defaults to `false`
skipPOMs | Skip goal on POM artifacts | No; defaults to `true`
If you use the `dataSet` element, you'll need to populate it with a one or
more `data` elements. A `data` element is used to specify a directory, a
tarball archive, or a file. You can add as many data
elements to your dataSet as you'd like. The `data` element has the
following options:
Element | Description | Required
---------------- | ---------------------------------------------------------------------------- | ------------------------------------
src | The directory, tarball, file to include in the package | Yes
dst | New filename at destination (type must be `file`) | No
linkName | The path of the link (type must be `link`) | Yes for link
linkTarget | The target of the link (type must be `link`) | Yes for link
symlink | Indicate if the link is a symblolic link (type must be `link`) | No; defaults to `true`
type | Type of the data source. (archive, directory, file, files, link or template) | No; but will be Yes in the future
missingSrc | Fail if src file/folder is missing (ignore or fail) | No; defaults to `fail`
includes | A comma seperated list of files to include from the directory or tarball | No; defaults to all files
excludes | A comma seperated list of files to exclude from the directory or tarball | No; defaults to no exclusions
conffile | A boolean value to define if the files should be included in the conffiles | No; defaults to `false`
mapper | The files to exclude from the directory or tarball | No
paths/(path..) | One or more string literal paths that will created in the package | No; Yes for type `template`
There are different kinds of mappers that can be selected via the `type` argument. The most common one is the 'perm' mapper.
Element | Description | Required
------------- | ----------------------------------------------------- | -----------------------
type | 'perm' | Yes
prefix | Add this prefix to the files | No; defaults to ""
uid | Numerical uid | No; defaults to 0
gid | Numerical gid | No; defaults to 0
user | User name | No; defaults to "root"
group | User group | No; defaults to "root"
filemode | File permissions as octet | No; defaults to 644
dirmode | Dir permissions as octet | No; defaults to 755
strip | Strip n path components from the original file | No; defaults to 0
Below is an example of how you could configure your jdeb maven plugin to
include a directory, a tarball, and a file in your deb package and then sign it with the key 8306FE21 in /home/user/.gnupg/secring.gpg:
```xml
<build>
<plugins>
<plugin>
<artifactId>jdeb</artifactId>
<groupId>org.vafer</groupId>
<version>1.8</version>
<executions>
<execution>
<phase>package</phase>
<goals>
<goal>jdeb</goal>
</goals>
<configuration>
<signPackage>true</signPackage>
<signMethod>dpkg-sig</signMethod>
<signRole>builder</signRole>
<keyring>/home/user/.gnupg/secring.gpg</keyring>
<key>8306FE21</key>
<passphrase>abcdef</passphrase>
<dataSet>
<!-- Tarball example -->
<data>
<src>${project.basedir}/target/my_archive.tar.gz</src>
<type>archive</type>
<includes>...</includes>
<excludes>...</excludes>
<mapper>
<type>perm</type>
<strip>1</strip>
<prefix>/somewhere/else</prefix>
<user>tcurdt</user>
<group>tcurdt</group>
<filemode>600</filemode>
</mapper>
</data>
<!-- Directory example -->
<data>
<src>${project.build.directory}/data</src>
<type>directory</type>
<includes/>
<excludes>**/.svn</excludes>
<mapper>
<type>ls</type>
<src>mapping.txt</src>
</mapper>
</data>
<!-- File example -->
<data>
<src>${project.basedir}/README.txt</src>
<dst>README</dst>
<type>file</type>
<missingSrc>ignore</missingSrc>
</data>
<!-- Multiple files example -->
<data>
<type>files</type>
<paths>
<path>README.txt</path>
<path>CHANGES.txt</path>
</paths>
<dst>/var/lib/${artifactId}</dst>
</data>
<!-- Template example -->
<data>
<type>template</type>
<paths>
<path>/etc/${artifactId}</path>
<path>/var/lib/${artifactId}</path>
<path>/var/log/${artifactId}</path>
<path>/var/run/${artifactId}</path>
</paths>
</data>
<!-- Hard link example -->
<data>
<type>link</type>
<linkName>/a/path/on/the/target/fs</linkName>
<linkTarget>/a/link/to/the/scr/file</linkTarget>
<symlink>false</symlink>
</data>
<!-- Symbolic link example -->
<data>
<type>link</type>
<linkName>/a/path/on/the/target/fs</linkName>
<linkTarget>/a/sym/link/to/the/scr/file</linkTarget>
<symlink>true</symlink>
</data>
<!-- Conffiles example -->
<data>
<src>${project.build.directory}/data</src>
<type>directory</type>
<includes/>
<excludes>**/.svn</excludes>
<conffile>true</conffile>
<mapper>
<type>ls</type>
<src>mapping.txt</src>
</mapper>
</data>
</dataSet>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
```
If you don't want to store your key information in the POM you can store this in your settings.xml, here's an example settings.xml:
```xml
<settings>
<profiles>
<profile>
<id>jdeb-signing</id>
<properties>
<jdeb.keyring>/home/user/.gnupg/secring.gpg</jdeb.keyring>
<jdeb.key>8306FE21</jdeb.key>
<jdeb.passphrase>abcdef</jdeb.passphrase>
</properties>
</profile>
</profiles>
<activeProfiles>
<activeProfile>jdeb-signing</activeProfile>
</activeProfiles>
</settings>
```
keyring, key and passphrase can then be omitted from the POM entirely.
|
