Re:Using Java 9 Modularization to Ship Zero-Dependency Apps
by greenhouse_gas on Wednesday January 03, 2018 @12:19AM
(#16058661)
I've never used Maven, only gradle.
The issue with convention over configuration is that you don't see how things should happen, because they're hidden behind the convention.
For example, what are the steps behind your Android build? Can you tell me exactly what steps gradle takes when you run gradlew assembleDebug?
So if for whatever reason you need to modify something, you're completely on your own.
Re:Using Java 9 Modularization to Ship Zero-Dependency Apps
by frant-hartm on Wednesday January 03, 2018 @07:38AM
(#16060470)
Sure..
$ gradlew -m assembleDebug
Learn the tools you use..
— Maven is simple, not arcane. I’ve produced countless “custom” builds with wild variations of need and never has Maven let me down. In some sense this is easy to prove (see maven-antrun-plugin); however, Maven’s core plugin/idioms supports 90+% of use cases I’ve seen over many many “weird” build requirements. To your example, “copying files” is fundamental; however you have to learn the idiomatic way to do it if you want to reap the benefits. Otherwise, just call out to maven-antrun- or similar. But then you’re chasing your tail.