Curious as to where stable builds are and dev builds are?
axemwa opened this issue ยท 7 comments
Curious as to where stable builds are and dev builds are. Are the stable builds on spigotmc or bukkitdev as I noticed that multiverse on spigot was last updated in 2016, multiverse on bukkitdev was last updated in 2017 and the multiverse in this link https://ci.onarandombox.com/job/Multiverse-Core/ was last updated in 2018
So jenkins builds is classed as a stable build then? If not where would safer/more stable builds be dev bukkit?
A lot of plugin devs seem to be a bit iffy with the new "Vector" system and aren't updating that's all, so I'm trying to choose which build would suit most plugins preferably a stable build
I'm not even sure what the "Vector" system is. I think we're at a very interesting point in Minecraft Plugin age. This project was started when @Rigby90 and I were in school, with gratuitous amounts of free time while not in school, that's how it was for a lot of us.
That brings the life of a lot of the "big" plugins to ~7.5 years (give or take a year or two). I know @dumptruckman still hangs out here, I watch for emails detailing security issues or API breakage, so we're all still watching the repositories but we don't hang out in IRC every day (like I used to ha) because there are other things to learn and contemplate.
- You're right, we should probably push a new build up to the upstream systems (It's just annoying that there isn't a "true" source like PyPi, PPA or NPM), but that takes us remembering. Jenkins is just so easy to push to.
- What is "Vector", by the quotes and capitalization, I assume this is some new kind of API or hook? Or is it just a new deployment repository? I think it's fair to say that at this point we don't have the time to re-write Multiverse for a new API, but pushing it to a new location might be feasible.
Vector system I'm pretty sure it's just a class/class name change, not 100% sure but here's the build for worldguard mentioning it http://builds.enginehub.org/job/worldguard/10556
So this looks like an internal API Change, and you're really just asking to update the WorldEdit API.
IIRC this (might) only be a thing for MV portals and has nothing to do with Core.
Note our dependency POMs:
Core (No WorldEdit dep)
Portals
With all of this said, I'm not sure what this means, good or bad... It's going to suck if plugins who want to interface with something like WorldEdit have to choose between old Vector / new BlockVector3 if they don't have a compatibility layer. We do use Vector in: https://github.com/Multiverse/Multiverse-Portals/blob/master/src/main/java/com/onarandombox/MultiversePortals/WorldEditConnection.java but that's the only place I think. From a cursory glance at your posted link it should be a drop-in replacement, but that will probably break all old WorldEdit compatibility. I'm not against this as long as the WE team doesn't decide to change back or something. I imagine that's the reason for your statement:
be a bit iffy with the new "Vector" system
This is a huge reason we're hesitant to make big changes to MV; I'd prefer to keep what we have and let other plugins who use our API do their thing and not be broken :(