One way in which this could be slightly more minimal is to remove the mvnw wrapper.
Honestly if you want to do development on a Java/Maven project, I don’t think it’s unreasonable to have Java and Maven installed. The wrapper adds three directory entries to the top-level repo directory, and is lots of copy/pasted code.
It's absolutely unreasonable to expect that, and the wrapper should stay. I don't have Maven installed anywhere, and i don't have Gradle on the global path, because i work on projects which require different versions of Gradle.
Saying that removing this would make the project more minimal seems deeply confused to me. Minimalism is not measured in the number of directory entries at the top level, but by the amount of stuff the user has to understand. Taking the wrappers out does not reduce that.
it’s all a balance. i’m obsessive, yeah, but i’m also trying to have a bit of balance for the bigger picture to each choice. if you look back a few commits you’ll see where i wasn’t even using maven, just GNU Make! But i was convinced over time that taking a more conventional route for that would yield better returns.
Honestly if you want to do development on a Java/Maven project, I don’t think it’s unreasonable to have Java and Maven installed. The wrapper adds three directory entries to the top-level repo directory, and is lots of copy/pasted code.