[alejo]

I have tried twice in the past 5 years or so to convert different projects (mostly Java) to Bazel but failed miserably every single time.

I do not have notes handy so I don’t remember exactly what happened but my impressions after a week or two invested trying to get it running were a) that our projects had too many unsupported things (dependencies, flows) that would require a huge effort to adapt; and b) that it would take way too much effort for our small team to convert the 500+ repos we were building to release our software.

I have always dreamed of a time in which I’m able to fin a tool that fills this gap. Man, not having to build the same code that hasn’t changed over and over locally and in pipelines sounds so appealing.

[jsiepkes]

> Man, not having to build the same code that hasn’t changed over and over locally and in pipelines sounds so appealing.

Can't you use something like Maven build cache ( https://maven.apache.org/extensions/maven-build-cache-extens... ) for that?

[alejo]

I somehow have never seen this. Will try it out, thanks

[woooooo]

Java seems like a particularly bad case to migrate for a non-google-size company, how does it even work? Do you have to check in every maven dependency to the monorepo as source?

[oftenwrong]

No, you can use https://github.com/bazelbuild/rules_jvm_external