| commit | b64497d3fbbd66f5f509b04a6e60fcc82f1dd518 | [log] [tgz] |
|---|---|---|
| author | Damien Martin-Guillerez <damienmg@users.noreply.github.com> | Sun Mar 19 15:37:52 2017 +0100 |
| committer | GitHub <noreply@github.com> | Sun Mar 19 15:37:52 2017 +0100 |
| tree | a403c4ed839e8b8311782f7038266409554e14f1 | |
| parent | 6ff4e3afde037626526ca20e66bc4d091fde2bca [diff] |
Remove third_party (#49) Use Bazel fetching capacity instead. After this change, one needs to `bazel build //com.google.devtools.bazel.e4b` in order to have the runfiles for the plugin resolved (and the jar fetched).
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.
This plugin was tested with Eclipse Mars (4.5) but should also work with Eclipse Neon (4.6).
To import an existing Bazel project or start a new one, go to “New” > “Project...” > “Others”.
See our contributing page to get some idea on what missing features need help on.