lmao java has as many build tools as python has packaging tools. when given the options of "IntelliJ", "Maven", and "Gradle", I foolishly went with IntelliJ on the grounds that it's the IDE already so presumably it works the best for this fucking around that doesn't have to work for anybody else anyway. unfortunately things like Kotlin compiler plugins have Maven snippets or Gradle snippets or both but never IntelliJ instructions, even the first-party Kotlin compiler plugins made by the same company as IntelliJ. clearly Kotlin is so inspired by Swift that it's equally impossible to use.

when i said party like it's 2009 i did not mean writing Java 6 but i guess that's where we're headed (although i will not go that far back, it looks like Java 18 finally established UTF-8 as the default in March 2022). if you're curious yes i was writing Swing applications in 2009 as a sixth grader, but not as Melody so you can't have the link (but it's in here if you're extremely bored)


You must log in to comment.

in reply to @cactus's post:

nothing is going to have support for IJ's build system because it's IJ specific, not something portable or scriptable or even useful beyond "hi i have java files i want to open in IJ that aren't already set up Properly"
(not to take away from the overall point, java build systems suck and the ecosystem is unfun, just wanted to try clear things up a little)
(if you're still wondering what to use, i'd recommend gradle w/ kotlin buildscript, but ymmv)

If you like XML, you should use Maven. If you don't like XML, you should still use Maven, because Gradle is made by sadists, and as far as I can tell, its fanbase consists, fittingly, exclusively of masochists.

A good IDE will be able to consume a Maven project definition (โ€œPOMโ€) and generate its own internal project definition from that. You write/edit the POM, the IDE syncs to that.