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

Macro-support workaround breaks IntelliJ plugin #81

Closed
gkossakowski opened this issue Oct 11, 2017 · 7 comments
Closed

Macro-support workaround breaks IntelliJ plugin #81

gkossakowski opened this issue Oct 11, 2017 · 7 comments

Comments

@gkossakowski
Copy link

Apparently, the pattern bazel-deps uses to get around ijar+scala macros issue confuses the IntelliJ plugin. The problem is with using "//jar:file".

See the corresponding issue in the intellij plugin: bazelbuild/intellij#142
I'm cross-posting between repos because it's not clear whether this issue should be fixed by bazel-deps, the intellij plugin or maybe even bazel core.

The discussion which points at bazel-deps as a source of problem is here: bazelbuild/intellij#97 (comment)

@johnynek
Copy link
Collaborator

we have to do it this way until the scala rules can support macros in jars. maven_jar will not work.

The solution is in the scala rules to make a scala_jar repository rule which can not use ijar on the output, but give a sane java_provider.

@ittaiz
Copy link

ittaiz commented Oct 11, 2017 via email

@gkossakowski
Copy link
Author

Ittai, Do you have a sense of how much work is left?
Our homegrown aspects that generate intellij project files are subtly broken by recent bazel/rules_scala upgrade and i'm trying to estimate whether i should dive into fixing them

@gkossakowski
Copy link
Author

I found a workaround for our internal issues so I'm not on fire anymore but still very interested in getting the official intellij plugin to work.

@ittaiz
Copy link

ittaiz commented Oct 12, 2017 via email

@kevingessner
Copy link
Contributor

I believe #101 has fixed this -- scala deps work in intellij for me these days.

@johnynek
Copy link
Collaborator

johnynek commented Mar 6, 2018

reopen if there is an issue.

@johnynek johnynek closed this as completed Mar 6, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants