Re:Building a Build System: Bazel Reaches Beta
by GauntletWizard on Wednesday September 09, 2015 @07:49PM
(#10195398)
Bazel's opinionated nature is it's blessing and curse. If you follow it's rules (fairly simple, internally consistent, and well thought out), it's amazing, and you need think a lot less about "where does this file go?", etc. If you don't have all those rules in your head, or if you're inconsistent about them, it's a nightmare.
Thankfully, it's a nightmare that can be fixed, and it behooves you to do so: Bazel's simple artifacts and build speedups are well worth the time you spend converting to it.
Re:Building a Build System: Bazel Reaches Beta
by skybrian on Wednesday September 09, 2015 @06:38PM
(#10195126)
Actually, that's not Maven. In Maven, each project has its own java directory. With Blaze (and I assume Bazel), Java libraries from entirely different projects all live in the same giant java and javatests subtrees. Behold the glory of the monolithic repository!
It figure this out, I had to patch Bazel with printlns where tries to find all the tests.
A coworker found a similar issue with assumptions around the project layout, but I can't remember what it was. Being that Bazel is was Alpha at the time, now Beta, I am not going to write it off yet. If nothing else, better documentation about assumed layouts would be great.