-
Notifications
You must be signed in to change notification settings - Fork 14
Error compiling project with config_setting that supports "local" or "maven" alias to jar deps #6
Comments
Any news on this? Should I be pulling the project and trying to fix locally to make progress on this issue? |
@psaville-google sorry, @dslomov is on holidays. |
@psaville-google Have you tried with Bazel @Head? |
Which Bazel version are you using? I checked and this should be fixed at HEAD, probably in |
My workspace is as follows: WORKSPACE:
java/BUILD:
Both
Work as expected. |
@kchodorow : I'm surprised that the dependency on |
@dmarting: I indeed forget about the e4b aspect and now I can actually repro it. Clickety-click... |
lberki, Your workspace isn't quite how I set it up. I'll clarify here just for WORKSPACE:
local/BUILD:
src/java/some-package/BUILD:
Thus, the some-package java can always depend on //external:liba. The eclipse project now needs to evaluate the //external:liba dependency as Thanks for working on this - much appreciated. |
Sorry for pinging a closed issue. When and how does your updatesite get updated, after change commits? Thanks. |
Manually :) but this was a problem on the Bazel side so it does not need On Thu, Sep 1, 2016, 10:17 PM psaville-google notifications@github.com
|
I pulled a local bazel repo clone and built bazel from HEAD yesterday in order to test if this is working with e4b. Sadly, it still doesn't work.
|
:/ Can you open a separate bug? |
…s a select. Fixes bazelbuild/eclipse#6 . -- MOS_MIGRATED_REVID=131698950
I have a bazel project in which I am using an alias rule to choose "local" java_import rules or the WORKSPACE maven_jar, based on a config_setting rule. The default is to use the maven_jar rule.
I get no errors when building with bazel directly. I get the following error in e4b:
Build and Workspace files look as follows
The text was updated successfully, but these errors were encountered: