| commit | 4d611f89b2d0a4bac0f10be01f9c305d57fb456a | [log] [tgz] |
|---|---|---|
| author | Damien Martin-Guillerez <dmarting@google.com> | Mon Apr 18 21:34:16 2016 +0200 |
| committer | Damien Martin-Guillerez <dmarting@google.com> | Wed Apr 27 12:02:47 2016 +0200 |
| tree | affa944fb96f6f60b746525cfc6be9f33ff0001e | |
| parent | 62714054b0453a4f9e28b7ee8835ca3c739d3612 [diff] |
Initial import of e4b, an Eclipse plugin for Bazel This is really rudimentory. It simply supports creating the classpath from a project. You can create a new Bazel project with New project > Import Bazel project Then you can select the list of targets you want to build and the list of directories you want to track. Fixes bazelbuild/bazel#12. Change-Id: I7b33931ebc4539ff3070c6e68d43587a52674d07
e4b is an Eclipse plugin for Bazel. It is really rudimentary. It simply supports creating the classpath from a project and using Bazel for incremental builds..
You can create a new Bazel project with New project > Import Bazel project Then you can select the list of targets you want to build and the list of directories you want to track.
It is highly experimental and support is minimal. However, we are happy to accept contribution to make this support grows to a better shape.
Interesting feature to add is first to be able to launch test from Eclipse, correctly adding the eclipse debugger to the JVM.
Second, better support for BUILD file would be interesting. Maybe using Xtext.
Finally, the code is completely missing tests and improving the test coverage would be great.