@Flibio
Unfortunately the problem is a rather general one with the way your plugin works. As long as no other plugin (or with SpongeVanilla: the plugin loader itself) is accessing any annotation via reflection on the plugin class your plugin will fail to load, because in that case it will try to load your annotation class before your plugin is loaded.
Therefore, the same problem can be reproduced on SpongeForge with one of these plugins:
Running any of these plugins on a SpongeForge servers results in the following similar crash report:
The reason why this always happens on SpongeVanilla is that unlike SpongeForge, SpongeVanilla is currently loading the plugin metadata directly from the annotation using reflection. This might be replaced later on, but for now this would be a general problem, because your plugin can never load on SpongeVanilla, unless it is loaded before all other plugins.
I have an Ideaā¦ put 01 in front of the jar nameā¦ Sponge loads mods alpha-numeric by file nameā¦ numbers first. Itās a quick fix until Sponge can fix that dependency handling thingā¦ thatās going to become rather important as more plugins depend on each other.
While that does indeed fix the issue currently, this is a temporary workaround this is going to be removed as soon as plugin dependencies are implemented.
@Flibio
Now that he mentioned that, one possible fix would be of course to simply have all plugins using Updatifier specify an optional dependency on it, so as soon as this is implemented in SV, it would always load Updatifier first, and therefore we wouldnāt have any problems with inexistent classes anymore.
Added commands to check updates from a player who has updatifier.notify permission, or the console
Added clickable links for players who get notified
Added an api jar which other plugins could ship and interact with Updatifer.
Note: To make Updatifer work on SpongeVanilla, the plugin that uses Updatifier must ship Updatifer api jar, which is available on jitpack maven. Documentation will come later.
I am a bit confused. I ran both EconomyLite with Updatifier installed on my server, and it refused to start. Is this intended? Am I not meant to install Updatifier itself on the server?
One of the plugins using Updatifier forgot to follow the wiki and add Updatifier as an after dependency: dependencies = "after: Updatifier". Iāll investigate and try to figure out who it was.
I think Iām doing something wrong. After running some tests with PJP, I noticed that Updatifier is not detecting new updates. The git tag matches the plugin version as per your wiki, but the only time Iāve actually seen it work is last night when I accidentally created a git release with an invalid tag (tag "v0.9.38 should have been ā0.8.38ā). Can you review my git page please?
Are you updating to API version 4 soon? The dependency declaration in @Plugin(...) has changed. Is the version of this plugin ā1.3.1ā or āv1.3.1ā?