-
Notifications
You must be signed in to change notification settings - Fork 6
Expand file tree
/
Copy pathpom.xml
More file actions
217 lines (204 loc) · 10.1 KB
/
Copy pathpom.xml
File metadata and controls
217 lines (204 loc) · 10.1 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
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
<?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>
<!--
"Batteries-included" convenience aggregate. Depending on this single
artifact pulls the default PDF stack (graph-compose = graph-compose-core +
graph-compose-render-pdf), the built-in document templates, the bundled
Google fonts, and the colour-emoji set — the one-line install for newcomers
who want everything wired up. The office backends (render-docx / render-pptx)
stay opt-in and are NOT bundled. Power users instead depend on the individual
coordinates and pick their own font/emoji versions.
Versioning: this module tracks the ENGINE line (its version == the engine
version, bumped in lockstep), and pins specific graph-compose-fonts and
graph-compose-emoji versions (those two release on their own tag lines). It
is standalone (no Maven parent) and packaged as an empty `jar` carrying only
<dependencies> — like the graph-compose wrapper — NOT `pom`: a `pom` would
force every consumer to add `<type>pom</type>` and break a plain-dependency
copy-paste. Carrying no sources, it publishes the main jar + signed pom (the
source/javadoc plugins skip an empty source set) — the same artifact set as
the graph-compose wrapper, which Central accepts.
-->
<groupId>io.github.demchaav</groupId>
<artifactId>graph-compose-bundle</artifactId>
<!--
Tracks the engine line (== the engine version in the repo); the release-cut
`versions:set` bumps engine + bundle to the release version in lockstep, while
graph-compose-fonts / graph-compose-emoji stay on their own lines. The
graph-compose and graph-compose-templates dependencies below use
${project.version}, so they follow automatically.
-->
<version>2.1.1-SNAPSHOT</version>
<packaging>jar</packaging>
<name>GraphCompose Bundle</name>
<description>Batteries-included aggregate: the default PDF stack (engine + PDF backend), the built-in document templates, the bundled Google fonts, and the colour-emoji set at compatible versions.</description>
<url>https://github.com/DemchaAV/GraphCompose</url>
<licenses>
<license>
<name>MIT License</name>
<url>https://opensource.org/licenses/MIT</url>
<distribution>repo</distribution>
</license>
</licenses>
<developers>
<developer>
<id>DemchaAV</id>
<name>Artem Demchyshyn</name>
<email>demchishynartem@gmail.com</email>
<url>https://github.com/DemchaAV</url>
<roles>
<role>Lead Developer</role>
<role>Architect</role>
</roles>
<timezone>UTC 0</timezone>
</developer>
</developers>
<scm>
<connection>scm:git:https://github.com/DemchaAV/GraphCompose.git</connection>
<developerConnection>scm:git:ssh://git@github.com/DemchaAV/GraphCompose.git</developerConnection>
<url>https://github.com/DemchaAV/GraphCompose/tree/main</url>
</scm>
<properties>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
<maven.compiler.release>17</maven.compiler.release>
<!-- Pinned bundled-fonts / colour-emoji versions this bundle ships with.
Both release on their own tag lines (fonts-v* / emoji-v*), so they are
pinned here rather than tracking ${project.version}. -->
<graphcompose.fonts.version>1.0.0</graphcompose.fonts.version>
<graphcompose.emoji.version>1.0.0</graphcompose.emoji.version>
<maven.compiler.plugin.version>3.15.0</maven.compiler.plugin.version>
<maven.jar.plugin.version>3.5.1</maven.jar.plugin.version>
<maven.source.plugin.version>3.4.0</maven.source.plugin.version>
<maven.javadoc.plugin.version>3.12.0</maven.javadoc.plugin.version>
<maven.gpg.plugin.version>3.2.8</maven.gpg.plugin.version>
<central.publishing.plugin.version>0.11.0</central.publishing.plugin.version>
<gpg.skip>true</gpg.skip>
</properties>
<dependencies>
<!-- The default PDF stack: the graph-compose wrapper pulls graph-compose-core
+ graph-compose-render-pdf, so a bundle consumer renders PDF out of the box. -->
<dependency>
<groupId>io.github.demchaav</groupId>
<artifactId>graph-compose</artifactId>
<version>${project.version}</version>
</dependency>
<!-- The built-in CV / cover-letter / invoice / proposal templates. -->
<dependency>
<groupId>io.github.demchaav</groupId>
<artifactId>graph-compose-templates</artifactId>
<version>${project.version}</version>
</dependency>
<!-- The bundled fonts, at the pinned independent fonts version. -->
<dependency>
<groupId>io.github.demchaav</groupId>
<artifactId>graph-compose-fonts</artifactId>
<version>${graphcompose.fonts.version}</version>
</dependency>
<!-- The colour-emoji set, at the pinned independent emoji version. -->
<dependency>
<groupId>io.github.demchaav</groupId>
<artifactId>graph-compose-emoji</artifactId>
<version>${graphcompose.emoji.version}</version>
</dependency>
</dependencies>
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<version>${maven.compiler.plugin.version}</version>
<configuration>
<release>${maven.compiler.release}</release>
</configuration>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jar-plugin</artifactId>
<version>${maven.jar.plugin.version}</version>
</plugin>
</plugins>
</build>
<profiles>
<!--
Maven Central release. This module carries no sources, so the
source/javadoc plugins skip an empty source set (failOnError=false keeps
javadoc from aborting) and only the main jar + signed pom are uploaded —
the same artifact set as the graph-compose wrapper. Activated with
`-P release`; the publish workflow flips -Dgpg.skip=false on the engine
`v*` tag (the bundle ships together with the engine it pins).
-->
<profile>
<id>release</id>
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-source-plugin</artifactId>
<version>${maven.source.plugin.version}</version>
<executions>
<execution>
<id>attach-sources</id>
<phase>package</phase>
<goals>
<goal>jar-no-fork</goal>
</goals>
</execution>
</executions>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-javadoc-plugin</artifactId>
<version>${maven.javadoc.plugin.version}</version>
<executions>
<execution>
<id>attach-javadocs</id>
<phase>package</phase>
<goals>
<goal>jar</goal>
</goals>
<configuration>
<failOnError>false</failOnError>
<quiet>true</quiet>
</configuration>
</execution>
</executions>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-gpg-plugin</artifactId>
<version>${maven.gpg.plugin.version}</version>
<executions>
<execution>
<id>sign-artifacts</id>
<phase>verify</phase>
<goals>
<goal>sign</goal>
</goals>
<configuration>
<skip>${gpg.skip}</skip>
<gpgArguments>
<arg>--pinentry-mode</arg>
<arg>loopback</arg>
</gpgArguments>
</configuration>
</execution>
</executions>
</plugin>
<plugin>
<groupId>org.sonatype.central</groupId>
<artifactId>central-publishing-maven-plugin</artifactId>
<version>${central.publishing.plugin.version}</version>
<extensions>true</extensions>
<configuration>
<publishingServerId>central</publishingServerId>
<autoPublish>false</autoPublish>
<waitUntil>validated</waitUntil>
</configuration>
</plugin>
</plugins>
</build>
</profile>
</profiles>
</project>