Releases: salesforce/bazel-eclipse
BEF 1.2.1 September 2020
This is a patch release. It is highly recommended to upgrade to this version.
Notable Change:
- This release fixes a major user experience issue during iterative development. In prior releases, the IDE would sometimes pause to wait for the underlying Bazel workspace to build even though there were no changes on the file system. The root cause was BEF invoking an Eclipse API, which we discovered has the side effect of causing a project rebuild. We were able to optimize out almost all calls to that API. See Issue #145 for details.
BEF 1.2.0 June 2020
This is a major release, with these updates:
Notable changes
- Bazel packages are now imported in the correct reverse dep order (A imported before B, if B depends on A) which makes it possible to compute the Java classpath just once (improves performance, correctness)
- Bazel test dependencies are now assigned to the Eclipse JDT test classpath. Before, they were added to the main JDT classpath. This ensures main classes cannot access test classes (e.g. JUnit, Mockito) for code completion in the Java editor.
- src/main/resources and src/test/resources directories are now imported as Eclipse source folders
- Support alternate legal filenames for Bazel config files WORKSPACE.bazel and BUILD.bazel
Release Notes:
- We worked on improving the speed of the initial import of a Bazel workspace into Eclipse in 1.2.0, but performance is still unacceptable. This is a top issue in the following 1.2.5 release.
- We worked on refreshing the classpaths of affected projects if a BUILD file changed, but performance was unacceptable for iterative development as the logic triggered too often. This feature is disabled, and is a top issue for the 1.2.5 release. Changes to BUILD files will require re-importing the workspace until then.
To view future release roadmaps, navigate to the Projects section of this GitHub repo. Bugs and missing features are found in the Issues section.
BEF 1.1.0 March 2020
BEF 1.0.4 January 2020
This release adds support for packages with these rules:
- java_proto_library
- java_lite_proto_library
- java_grpc_library
These packages can now be imported into BEF as projects. Additionally, the generated jars from these rules are now added to the classpath of any consuming project. See Issue #37 for details.
BEF 1.0.3 January 2020
This release addresses a single issue:
- #54: version incompatibility with BEF imported org.json package causes exception in org.json.JSONTokener during import of a Bazel workspace.
BEF 1.0.2 January 2020
This patch release to 1.0.1 addresses two issues:
- Source jar attachments now work for external jar dependencies. If you navigate to a type declaration for an upstream maven jar (e.g. spring framework), BEF will now correctly locate the source jar and Eclipse JDT will now display the source code for that dependency. (Issue #17)
- Bazel workspaces that rely on implicit java test dependencies (--explicit_java_test_deps=false) will now import correctly, with BEF adding the implicit dependencies to the classpath of projects as needed (Issue #43)
BEF 1.0.1 December 2019
BEF 1.0.0 December 2019
December 2019 - Initial Release
Just in time for BazelCon 2019, the Salesforce team offers the initial public release of the BEF. This release offers solid support for conforming Java packages (see the docs for details on what that means).
Download the updatesite .zip artifact and follow the installation guide here:
https://github.com/salesforce/bazel-eclipse/blob/master/docs/install.md
Known issues: