Re:Mill: A fast JVM build tool for Java and Scala
by lihaoyi on Monday October 28, 2024 @05:48PM
(#41976750)
You can, but why should you need to? Why can't the build tool take the plugin code directly off of disk, build it, and use it? This kind of orchestration of manual steps is what build tools are meant to be good at
Re:Mill: A fast JVM build tool for Java and Scala
by cyberax on Monday October 28, 2024 @06:18PM
(#41977059)
Sure. But adding ability to self-modify the build drastically increases the complexity of a build tool. Maven developers decided that they want to avoid that.
Re:Mill: A fast JVM build tool for Java and Scala
by beeboobaa3 on Tuesday October 29, 2024 @01:59PM
(#41987500)
It can, for plugins. GP is talking about extensions which you typically don't need.
Re:Mill: A fast JVM build tool for Java and Scala
by dkarl on Tuesday October 29, 2024 @10:55AM
(#41984456)
Then you don't have a standard build, you have a build with multiple steps that needs to be documented and/or scripted. In an organization where every other project builds in a single step with "mvn package", and people can check out a repo and fire up their IDE and stuff just works, people are going to get bent out of shape because from their perspective, things aren't working out of the box.
A slightly more powerful build tool that supports custom code in the build doesn't force users to script around it. You can create an arbitrarily customized build that builds with the same commands as a Hello World project. (It's a double-edged sword, to be sure, because people don't try as hard to avoid customization as they would with Maven.)
You can just `mvn install` them locally into your local repository.