Glowstone VS Maven Wrapper

Assuming you mean this Glowstone, you'll see they themselves acknowledge that "it is not ready for survival".

It's definitely not a realistic replacement for modded Minecraft in general, since that's really hundereds of games and Mineclone only aims to replace Minecraft itself. For modded, I'm not sure what the answer is. Even most third party clients/servers that are compatible with vanilla Minecraft don't support Forge mods. Stevenarella might support Forge to some extent, but I'm not sure how it works since Forge is written in Java and Stevenarella is written in Rust. I'm not aware of any third party servers that support Forge in any capacity, but Glowstone (which actually seems like a pretty good third party server by the way) does support Bukkit plugins.

Also to add to this, if you don't need full vanilla functionality and are more focus on higher player count than something slightly more experimental but more performant might be your best bet like GlowstoneMC (glowstone supports paper plugins) or Minestrom

You could. Glowstone is a Minecraft server written in Java (without any of Mojang's code) but it is still not feature complete from what I heard, so things are missing. When I tried it, it seemed pretty solid and fast though.

I forked a project [1] in 2015 to remove Gradle, and it then quickly subsumed the original project, remaining under active development to this day.

There were other reasons, but de-gradling was one of the main motivations for my fork, and among the first of the major changes I made. The project is an implementation of an API which was discontinued by the original developers, but initially was built using Maven.

After switching from Gradle (which the project switched to in 2014) back to Maven, build times significantly decreased and development became much more pleasant. I found Gradle to be like a speed bump slowing down development, and reverting back to Maven was like a breath of fresh air. Simple, straightforward, and fast. Maven may not be perfect, but it does the job well.

[1] An open source Bukkit server implementation, https://github.com/GlowstoneMC/Glowstone -> http://github.com/GlowstonePlusPlus/GlowstonePlusPlus

Maven also has the maven wrapper: https://github.com/takari/maven-wrapper which accomplishes the same thing.

When creating a new Maven project, Micronaut also configures the Maven wrapper.

IDE's can be fiddly, and anyway I don't think it's good to depend on an IDE for building.

The project could have been set up instead with the "Maven wrapper"(1) which provides "mvn.cmd/sh" scripts at the top level of the project to fetch and run the proper Maven. So after cloning the project, all you have to do is set a proper JAVA_HOME and then do "./mvn clean package". The IDE's will then set themselves up properly if you import the project as a Maven project, and will sync with changes to the Maven pom.xml whenever it changes (Intellij does at least). That's really hard to beat.

(1) https://github.com/takari/maven-wrapper (Being integrated into Maven itself soon).

I got it from here: https://github.com/takari/maven-wrapper

> Now “obviously” the answer is that we should have pegged the version of gradle required to use the script

My first step with either gradle or maven is to install the wrapper generator, which has this effect. After adding the wrapper you invoke it via ./gradlew or ./mvnw in the project doirectory.

It’s not perfect - especially in terms of IDE support - but it’s crucial to at least keeping your CLI builds consistent across team members and in automation.

gradle wrapper: https://docs.gradle.org/current/userguide/gradle_wrapper.htm...

maven wrapper: https://github.com/takari/maven-wrapper