basically I have a submodule which provides server-internals utilities for the main module. The main jar has the submodule shaded in but how do I have it shade in the reobf'ed jar for the submodule
#How to install a spigot-obfed jar
steady heart
mystic gyro
Are you shading a reobf of your own plugin
steady heart
sure, yes
thing is I'm targeting multiple versions which need to be of'ed (1.17 and 1.18) so I can't just reobf the final jar, I have to shade in reobfed versions of the submodules
mystic gyro
Sounds to me like you might be using the wrong words
When you say shade reobf are you talking about spigot or your own plugin
What is reobfuscated
If it's Spigot you don't shade it
steady heart
I mean shading in a portion (a submodule of my own project) into the main jar of my own project
I am trying to reobf only the submodule and shade the reobfed submodule into the final jar
mystic gyro
I'm confused.. anyway are you using Maven or Gradle
steady heart
Maven
mystic gyro
Okay send your poms and tell me what isn't working
steady heart
relevant poms are Core/pom.xml, Nms-1_17_1/pom.xml and Nms-1_18/pom.xml
When I launch up the server I get a bunch of no class def errors such as net/minecraft/nbt/Tag which would likely be because my plugin isn't reobfed properly
mystic gyro
Could you send the entire error in a paste
steady heart
the only places where server internals are referenced are in the nms providers. This was run on a paper server; however, same error message is produced on a spigot server (1.18). I can rerun and grab a stacktrace on spigot if necessary.
mystic gyro
Hm try Spigot
steady heart
hmm
I mean ours poms look similar... I'm not sure what I'm missing. I don't need to reobf to mojang yet
steady heart
yeah no I'm not entirely sure why this ins't working? The poms seems to do the same thing (besides the mojang mappings)
steady heart
oh, fixed... apparently I was missing one of the <exectution> blocks