News for hackers. Stuff that matters.

A comment on Why I Moved Back from Gradle to Maven. Parent comment

Re:Why I Moved Back from Gradle to Maven by na85 on Tuesday April 03, 2018 @06:08PM (#16749840)
I guess I'd compile them like anything else: using Make to invoke the compiler.

Checking versions can be accomplished by using awk or another tool to compare output from $compiler --version.

What am I missing?

[ Parent | on HN ]
Re:Why I Moved Back from Gradle to Maven by sk5t on Tuesday April 03, 2018 @10:26PM (#16751383)
Your makefile / build script would grow so complex so as to start reimplementing maven or gradle.
[ Parent | on HN ]
Re:Why I Moved Back from Gradle to Maven by dcow on Tuesday April 03, 2018 @11:00PM (#16751532)
What if two things share a dependency?
[ Parent | on HN ]
Re:Why I Moved Back from Gradle to Maven by na85 on Tuesday April 03, 2018 @11:27PM (#16751635)
Do you mean a conflicting dependency in one of my 5 projects? If so, it's on me to pay that technical debt and fix my own crap.

If the dependency doesn't conflict, then my package manager takes care of it.

[ Parent | on HN ]
Re:Why I Moved Back from Gradle to Maven by pas on Wednesday April 04, 2018 @04:24AM (#16752998)
In the JVM world it's not uncommon to have different sets of versions of the same libraries for different but dependent projects. And it's not a problem, because classloading is hierarchical and so different versions can live side by side even inside one JVM.

And a lot of Java/Groovy/Scala/Kotlin libs are on Maven Central, but not packaged for let's say CentOS/Ubuntu/Debian/etc. So the package manager for JVM is Ivy (ivy2), or full Maven (which is basically ivy + a task runner).

[ Parent | on HN ]