tree 6ac77e0709b7a1422e240323b43d78b838c93bca
parent 56a7ae643059875a074ab6e3ca92754520483edd
author Leopold Schabel <leo@nexantic.com> 1607694830 +0100
committer Leopold Schabel <leo@nexantic.com> 1607694830 +0100

Remove .ijwb and .idea, migrate to import_run_configurations

The Bazel IntelliJ team has stated that while checking in the .ijwb folder
technically sorta-kinda works, they recommend against it since they cannot
guarantee any kind of backwards compatibility. Indeed, bootstrapping a
working IDE project from a clean checkout with .ijwb has been a
delicate matter in the past and is currently broken again.

Do the supported thing instead and nuke .ijwb and .idea and ignore them.
The .bazelproject file can then be used to create a new project using
File → Import Bazel project, creating the workspace from scratch.

Run configurations are now created by the Bazel plugin, and those XML
files come with a backwards compatibility promise.

This means that we lose all other shared settings except run
configurations. If there's particular configs that we want to keep, we
need to write custom tooling which mangles the XML configs, which will
allows us to deal with backwards compatibility and differences in
developer setups (i.e. outside contributors).

Test Plan:
Cloned the project from scratch, imported the Bazel
project, everything worked on the first try :O

X-Origin-Diff: phab/D658
GitOrigin-RevId: 979ac5345fd8a5f26a5f8ec3d5882ea477b48a69