v1_18 and v1_19_R1 NMS update

[q1445570795]

Add NMS v1_18_R1

[q1445570795]

This is the first time I use GitHub to submit code, so I'm not very proficient :)

[apatuka]

@q1445570795 Planning to update this for 1.19 ?

[ghost]

Hello,
Could you please provide your modification of the pom.xml file ?
Because as it is, it is impossible for someone else to compile your code.
Thanks in advance ! ^^

[q1445570795]

@q1445570795 Planning to update this for 1.19 ?
@apatuka
I have added nms, of course you can download the compiled .jar file from my homepage

[q1445570795]

@Sailoriae
Sorry, I didn't develop it by Maven.

Because the package and class names after version 1.17 are the same during my development, I can't compile,

Make 1.17, 1.18 and 1.19 unable to coexist):

I can only import one version package to compile

v1_ 18_ R1、v1_ 18_ R2、v1_ 19_ R1 cannot coexist. It must be deleted every time it is compiled, leaving only one

This method is stupid, just to make the plug-in available in the version

Can you understand me? My English is poor and I can't express it.

[ghost]

Thank you for your answer. In fact, the problem is that the structure of the project and of the pom.xml needs to be reviewed so that we can continue to compile with Maven. For example, we should take a look at what the Citizens developers do.
https://github.com/CitizensDev/Citizens2

[q1445570795]

About how I compile:
1.download Bukkit Files DragonTravel v01.008.02.jar
2.Compile NMS v1.18R1 v1.18R2 v1.19R1 one by one, generate jars, and only take v1_18_R1 and v1_18_R2 and v1_19_R1 class file
3.Open dragontravel v01.008.02 with WinRAR jar,
Path: \eu\phiwa\dragontravel\nms
Put the three compiled versions into it

[ghost]

I see... There is a way to automated all of this with Maven. I will try to do it, but for the moment I don't have the time.