Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Eclipse support #12

Closed
benmccann opened this issue Mar 24, 2015 · 12 comments
Closed

Eclipse support #12

benmccann opened this issue Mar 24, 2015 · 12 comments
Assignees
Labels
P2 We'll consider working on this in future. (Assignee optional) type: feature request
Milestone

Comments

@benmccann
Copy link

I'm hoping the Eclipse support can be open sourced :-) All the open-source build tools I currently use like Maven, Gradle, and SBT have Eclipse support built-in.

@damienmg
Copy link
Contributor

Ok I don't know if we ever going to ship the current Eclipse support but having an IDE support is definitely something high on our list

@cgruber
Copy link
Contributor

cgruber commented Mar 24, 2015

I've sort of generalized this in #31 beyond eclipse.

@damienmg damienmg added type: feature request P2 We'll consider working on this in future. (Assignee optional) labels Mar 26, 2015
@PerfectCarl
Copy link

interested in this too

@digulla
Copy link

digulla commented Sep 18, 2015

@damienmg Do you already have working support for Eclipse internally which you can't share? Or is the quality of the Eclipse support code just too poor to open it?

@damienmg
Copy link
Contributor

We have a Eclipse support internally that also include a lot of internal stuff such as integration with our control version system and it doesn't make much sense to open-source it (not that it is too poor, just not suited for outside Google).

@wrwg
Copy link

wrwg commented Nov 17, 2015

Eclipse (and IntelliJ) support can just mean being able to generate project files of the IDE via a command line. The IDEs typically listen for changes on their metadata, and then just magically update (at least Eclipse does).

Gradle eclipse and idea plugins do it this way, for example. I don't think it's too much work, but then it is still a bit too much if one just wants to use bazel.

@damienmg
Copy link
Contributor

No, why?

@wolfgangmeyers
Copy link

I have something that might help. Not quite a general purpose solution (the script only supports java and python, requires some hacking to customize for different projects), but I think it should be easy enough to adapt it to your needs. Basically it involves building _deploy jars that roll up all of the compile-time dependencies using bazel and then constructing eclipse files that reference those jar files. I may do some work to make this general-purpose and put it on github, but for now here is the work in progress - https://gist.github.com/wolfgangmeyers/49d8edaa763f5fcdcdf7

@dburnette
Copy link

As a former Googler (Eclipse/C++ user), I find it extremely painful using Bazel with a lack of Eclipse support :(. Even if the internal source control stuff can't/shouldn't be open sourced, dependency graph info and incremental build tools would be greatly appreciated!

@wolfgangmeyers
Copy link

Sounds like an eclipse plugin might be a better general solution. Providing an "import from existing bazel workspace" feature could then generate the project files from within eclipse.

@rohitsaboo
Copy link

As yet another ex-Googler on this thread, would love to see the Eclipse integration part open-sourced :) Also, if you have an idea how long this would take, it would be helpful to know.

@damienmg damienmg self-assigned this May 30, 2016
@damienmg damienmg added this to the 0.3 milestone May 30, 2016
@wolfgangmeyers
Copy link

Awesome!

bazel-io pushed a commit that referenced this issue Jun 10, 2016
This is no longer maintained and is now replaced by e4b:
  https://github.com/bazelbuild/e4b

Fixes #12.

--
MOS_MIGRATED_REVID=124545211
meteorcloudy added a commit to meteorcloudy/bazel that referenced this issue May 14, 2021
Patch support for overrides & git_override support
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P2 We'll consider working on this in future. (Assignee optional) type: feature request
Projects
None yet
Development

No branches or pull requests

9 participants