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

kotlin-compiler packages not found by IntelliJ #96

Closed
thewoolleyman opened this issue Jul 12, 2018 · 4 comments
Closed

kotlin-compiler packages not found by IntelliJ #96

thewoolleyman opened this issue Jul 12, 2018 · 4 comments

Comments

@thewoolleyman
Copy link

When I open the rules_kotlin repo itself, and go to a file which uses kotlin-compiler classes,
such as kotlin/builder/src/io/bazel/kotlin/compiler/BazelK2JVMCompiler.kt, IntelliJ fails to
resolve the import paths (see attached screenshot).

I'd like these to work, because it will help me find my way around and learn the APIs faster
when hacking on this project (to add kotlin-js support, as we discussed elsewhere).

I've played with this some, and I see the reference to the compiler as a dependency
in places like this.

I think the solution is to make it automatically included as a dependency in the generated .project/.blaze/modules/.workspace.iml module. However, I'm unsure of the proper way to go
about that.

Happy to hack on it some more, but I'd need pointers on how to proceed.

Thanks,
-- Chad

screen shot 2018-07-11 at 9 25 21 pm

thewoolleyman added a commit to thewoolleyman/rules_kotlin that referenced this issue Jul 12, 2018
...as a workaround to get IntelliJ to see the compiler imports.
See bazelbuild#96
thewoolleyman added a commit to thewoolleyman/rules_kotlin that referenced this issue Jul 12, 2018
...as a workaround to get IntelliJ to see the compiler imports.
See bazelbuild#96
@hsyed
Copy link
Contributor

hsyed commented Jul 12, 2018

Just to check, is the project synced up ? Top right corner, red icon with yellow dot in it.

I sm pushing a refactor to the sources and how they are built in a few hours.

@hsyed hsyed closed this as completed Jul 12, 2018
@hsyed hsyed reopened this Jul 12, 2018
@hsyed
Copy link
Contributor

hsyed commented Jul 12, 2018

@thewoolleyman I've just committed some changes. It should work much more reliably now.

@hsyed
Copy link
Contributor

hsyed commented Jul 13, 2018

Previous fix still had some problems. This last commit should work.

@hsyed
Copy link
Contributor

hsyed commented Aug 13, 2018

closing this as the problem no longer exists as far as I can tell.

@hsyed hsyed closed this as completed Aug 13, 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

2 participants