Support a Bazel Java project with multiple BUILD files (aka Wix 1:1:1) about bazel-eclipse HOT 2 CLOSED

What works with 1:1:1 as of today

With all the work that went into more flexible package layouts #8 our 1:1:1 support is actually pretty good. In fact, if the project is laid out such that:

• there is a root BUILD file that has a rule that rolls up all the subpackages
• the tests are defined in that root BUILD file

Everything works if you import just the root package as an Eclipse project. Even the test launchers. Like this (assume the toplevel BUILD is in projects/libs/oneoneone):

• BUILD (java_binary with deps on foo and bar libs, plus java_test rules) <== import this
• src/main/java/com/salesforce/foo/BUILD (java_library with Foo.java) <== do not import this
• src/main/java/com/salesforce/foo/Foo.java
• src/main/java/com/salesforce/bar/BUILD (java_library with Bar.java) <== do not import this
• src/main/java/com/salesforce/bar/Bar.java
• src/test/java/com/salesforce/baz/BazTest.java

For this case the main thing we need to change is the import offers. We should detect 1:1:1 and mask the subBUILDs because the user should not import src/main/java/com/salesforce/foo/BUILD or src/main/java/com/salesforce/bar/BUILD as distinct Eclipse projects. Just importing the root BUILD as an Eclipse project is enough.

What doesn't work

There are problems though if the tests are defined in a subBuild. The root BUILD will not have the test deps, nor the java_test rules. For example:

• src/test/java/com/salesforce/baz/BUILD (java_test for BazTest)
• src/test/java/com/salesforce/baz/BazTest.java

If this is the case, the test launchers when launching the file from the root BUILD project no longer work. Also the tests show compile errors if you open them from the root project.

I think for these cases we should:

• import the test subBUILD as an Eclipse project
• mask the test source dir from the root package project
• fix the name of the test package to make it clear what it is there for

from bazel-eclipse.

While there are ways to improve what we have, I think the 1:1:1 support is tolerable. As I wrote in #8, I have a new mindset that we shouldn't expect for BEF to perfectly model every Bazel build. Eclipse and JDT was not designed with the flexibility of Bazel in mind, and therefore it shouldn't be a surprise that more complex Bazel builds cannot be modeled in every case.

from bazel-eclipse.