-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathpom.xml
299 lines (262 loc) · 12 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
297
298
299
<?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>
<!--
We use Maven to build our plugin and Maven uses pom.xml to configure
itself.
This file is the heart and matter of everything that has to do
with how your plugin connects with other libraries and exports itself
when you want to publish it.
Please only edit options below, as the above declaration is machine
generated and not intended for user changes.
-->
<!-- ############################################################################### -->
<!-- Basic plugin configuration, start here -->
<!-- ############################################################################### -->
<!--
The Group ID represents the main package of your plugin
The Artifact ID represents the name of your plugin.
Traditionally, it is suggested to keep this name lowercase.
If your plugin uses spaces, please replace them with dashes (-) instead.
The Name represents the full name of your plugin
The Version is current version of your plugin. You want to update this continuously
-->
<groupId>org.example</groupId>
<artifactId>Potato</artifactId>
<name>Potato</name>
<version>1.0.0</version>
<!-- ############################################################################### -->
<!--
Configure some of the Maven settings. We also define
our new variables here such as the main class or Java version
for our plugin.
You can use those variables in your src/resources folder. See
plugin.yml folder there for example usage.
-->
<properties>
<!-- The full path to your plugin's main class, so that Spigot can find and load it -->
<main.class>org.main.Potato</main.class>
<!-- The Foundation version - change to latest version from https://github.com/kangarko/Foundation/releases -->
<foundation.version>5.7.6</foundation.version>
<!-- The Java version your plugin uses, see bstats.org for what most servers have and use that -->
<java.version>1.8</java.version>
<!-- How letters in your code should be saved on your disk, leave to UTF-8 to support all languages -->
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
<kotlin.version>1.4.30-M1</kotlin.version>
</properties>
<!--
Configure where should Maven look for other libraries and plugins we
want to use in our plugin. Those libraries and plugins can you then
reference below in the dependencies section.
Each repository has two parts - the id and url. The id does not
really matter, however the URL must contain a valid Maven repository
where the dependency is "installed" (that's why we call the goal "install"
because we want to install our plugin on our PC as well so that we can
use it in our other plugins together without linking it as a dependency)
By default we use the Spigot repository for Spigot and the central Maven
repo for many other plugins.
-->
<repositories>
<repository>
<id>spigotmc-repo</id>
<url>https://hub.spigotmc.org/nexus/content/groups/public/</url>
</repository>
<repository>
<id>jitpack.io</id>
<url>https://jitpack.io</url>
</repository>
<repository>
<id>sonatype</id>
<url>https://oss.sonatype.org/content/groups/public/</url>
</repository>
<repository>
<releases>
<enabled>true</enabled>
</releases>
<snapshots>
<enabled>false</enabled>
</snapshots>
<id>bintray.kotlin.eap</id>
<name>Bintray Kotlin EAP Repository</name>
<url>https://dl.bintray.com/kotlin/kotlin-eap</url>
</repository>
</repositories>
<pluginRepositories>
<pluginRepository>
<releases>
<enabled>true</enabled>
</releases>
<snapshots>
<enabled>false</enabled>
</snapshots>
<id>bintray.kotlin.eap</id>
<name>Bintray Kotlin EAP Repository</name>
<url>https://dl.bintray.com/kotlin/kotlin-eap</url>
</pluginRepository>
</pluginRepositories>
<!--
Configure what other libraries or plugins are we going to use in this plugin.
As a starting point, we are importing the Spigot API and Foundation.
-->
<dependencies>
<!--
Import the Spigot API since it's necessary for our plugin
Make sure you change the version to the latest version you want to use for your plugin.
-->
<dependency>
<groupId>org.spigotmc</groupId>
<artifactId>spigot-api</artifactId>
<!-- Change this to the latest version to stay up to date -->
<version>1.16.4-R0.1-SNAPSHOT</version>
<!--
The scope indicates if this library should be packaged together with our plugin
when we want to publish it.
Set this to "compile" if you want all classes from this library to be copied
to your plugin's jar, otherwise set this to "provided".
-->
<scope>provided</scope>
</dependency>
<!--
Import the Foundation library to kickstart our plugin development
-->
<dependency>
<groupId>com.github.kangarko</groupId>
<artifactId>Foundation</artifactId>
<version>${foundation.version}</version>
<!-- Include Foundation and its dependencies. There are exceptions, see shade plugin below -->
<scope>compile</scope>
</dependency>
<dependency>
<groupId>org.jetbrains.kotlin</groupId>
<artifactId>kotlin-stdlib-jdk8</artifactId>
<version>${kotlin.version}</version>
</dependency>
<dependency>
<groupId>org.jetbrains.kotlin</groupId>
<artifactId>kotlin-test</artifactId>
<version>${kotlin.version}</version>
<scope>test</scope>
</dependency>
</dependencies>
<!--
Configure what happens when we are building this project (Maven compiles our code into bytecode
for us automatically).
-->
<build>
<!--
When we are building your plugins, what plugins should we use during this process?
The plugins here extend the functionality of Maven, just like your plugin enhances Minecraft
These are not Minecraft plugins, but only Maven plugins!
-->
<plugins>
<!--
The first and the most essential plugin is the compiler, that translates your
human readable code into bytecode.
-->
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<!--
You want to check and update the latest version periodically from
https://mvnrepository.com/artifact/org.apache.maven.plugins/maven-compiler-plugin
-->
<version>3.8.1</version>
<configuration>
<source>${java.version}</source>
<target>${java.version}</target>
</configuration>
</plugin>
<!--
The second plugin is the shade plugin, packaging every library with
the "compile" scope (see dependencies)
-->
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-shade-plugin</artifactId>
<!--
You want to check and update the latest version periodically from
https://mvnrepository.com/artifact/org.apache.maven.plugins/maven-shade-plugin
-->
<version>3.2.1</version>
<executions>
<execution>
<phase>package</phase>
<goals>
<goal>shade</goal>
</goals>
<!--
By default we configure the Foundation to include itself and all classes when
we set the scope to compile (see above).
There are many libraries from Foundation we will not need to use, and here
can you specify which ones to exclude. Please leave the default ones as they are.
-->
<configuration>
<createDependencyReducedPom>false</createDependencyReducedPom>
<finalName>${project.name}-${project.version}</finalName>
<artifactSet>
<includes>
<include>org.mineacademy:Game*</include>
<include>com.github.kangarko:Foundation*</include>
</includes>
<excludes>
<exclude>org.mineacademy:GameAPI*</exclude>
</excludes>
</artifactSet>
<relocations>
<relocation>
<pattern>org.mineacademy</pattern>
<shadedPattern>${project.groupId}.${project.artifactId}.lib</shadedPattern>
<excludes>
<exclude>org.mineacademy.${project.artifactId}.*</exclude>
<exclude>org.mineacademy.gameapi.*</exclude>
<exclude>org.mineacademy.boss.*</exclude>
<exclude>org.mineacademy.worldeditbridge.*</exclude>
</excludes>
</relocation>
</relocations>
</configuration>
</execution>
</executions>
</plugin>
<plugin>
<groupId>org.jetbrains.kotlin</groupId>
<artifactId>kotlin-maven-plugin</artifactId>
<version>${kotlin.version}</version>
<executions>
<execution>
<id>compile</id>
<phase>compile</phase>
<goals>
<goal>compile</goal>
</goals>
</execution>
<execution>
<id>test-compile</id>
<phase>test-compile</phase>
<goals>
<goal>test-compile</goal>
</goals>
</execution>
</executions>
<configuration>
<jvmTarget>1.8</jvmTarget>
</configuration>
</plugin>
</plugins>
<!--
During the build, we are going to scan all files in src/main/resources
folder such as plugin.yml and your settings files and replace all variables
such as ${main.class} with their proper values.
You can use native variables such as ${project.X} or the ones you defined above
in the properties section.
-->
<resources>
<resource>
<directory>src/main/resources</directory>
<filtering>true</filtering>
</resource>
</resources>
</build>
</project>