Peter Laird

If I skimmed the issue/pr correctly, BEF can punt on addressing this and hide behind our [conforming java package](https://github.com/salesforce/bazel-eclipse/blob/master/docs/conforming_java_packages.md) limitation for now. But eventually this would be nice to fix.

Expanding this issue to cover any code generator, as the solution will likely be similar regardless of framework.

@beginningineer good question. I am thinking every Eclipse Bazel project will have second Eclipse classpath container "Bazel AutoDeps Classpath Container" that will contain the candidate list of deps. This will...

Progress has been made on this. While the Global Search Classpath feature #161 is experimental and still needs a lot of refinement, I believe it is the first step towards...

This feature is getting closer. Just after BEF 1.5.0 was released, I added a hook into JDT's _classpath fix_ extension point. This is the JDT UI scheme for presenting the...

Once this feature is done, we could take dependency management much further with something like [Fasten](https://github.com/fasten-project/fasten) which does detailed call-graph dependency analysis. I tried to do a quick POC with...

The IJ plugin devs have so far punted on the IDE project -> Bazel target -> classpath mapping problem. They have a single classpath for the entire workspace. https://github.com/bazelbuild/intellij/issues/179 But...

Added some doc notes to point to this issue. For example: https://github.com/salesforce/bazel-eclipse/blob/master/docs/bef/install.md#installing-a-jdk

The other workaround is to export JAVA_HOME in a shell, and launch Eclipse from that shell.

**Cause:** The first issue is the MavenProjectStructureStrategy failed to apply itself because the package is missing a src/test/java directory. This is fine, as it ultimately is a performance optimization. The...