Sounds like Greg’s main gripe with everything is y...
# kobalt
t
Sounds like Greg’s main gripe with everything is you need to execute code to understand the model of a build. be that gradle, kobalt, or basel. His argument being “I just just look at the pom.xml and see what dependencies are declared”, my angry stubborn fixation is that even with maven you need to evalutate and essentially “execute code” to resolve the pom ( including profiles which turn on/off based on env vars ) and parents etc. to get the resolved pom - in order to get a resolved/real view of the build. Which is probably me coming at it from a tooling perspective and not just a shallow view of “lets xpath some infomation out of the local pom only”.