Intellij: Support IntelliJ 2018.3

Created on 16 Oct 2018  路  13Comments  路  Source: bazelbuild/intellij

Just opening this issue so I can subscribe to when it is supported.

fixed pending release

Most helpful comment

The current code at head supports today's 2018.3 release. We'll upload a bazel plugin sometime next week built against 2018.3 as well.

All 13 comments

Agree, I'm really looking forward to the integrated profiler , sad that I cant hop on to the early access because bazel plugin is not working = (

https://github.com/uri-canva/intellij/pull/2 kinda works. At least enough to use the plugin for a java project. It's surely wrong in at least one way but let's your try 2018.3. Build with:

bazel build //ijwb:ijwb_bazel_zip --define=ij_product=intellij-ue-beta

Then install plugin bazel-bin/ijwb/ijwb_bazel.zip from disk.

2018.3 has been released. It would be great to be able to install the Bazel plugin! I'm new to plugin development but would be happy to jump in and try to help if anyone knows what work needs to be done.

Hey @drichelson I've been using the changes in https://github.com/uri-canva/intellij/pull/2/commits/273d4219cfee962d5cb09b56469199941448f869 with 2018.3.RC at work for the last few days. Had no problems. I only needed Java and Kotlin support so the Go, Scala and other languages might need changes. They compile at least.

Maybe a proper fix from upstream will appear someday soon. Guessing googler's were waiting for the release of 2018.3?

If you're chomping at the bit you could clone, cherry pick that commit and build using command above.

The current code at head supports today's 2018.3 release. We'll upload a bazel plugin sometime next week built against 2018.3 as well.

Be awesome if next time around support for the EAP could be merged.. Would it be crazy to have intellij-eap and "intellij-ue-eap in https://github.com/bazelbuild/intellij/pull/432/files#diff-9973c475d13c8599b6beba3d7c0bf6ef? With CI publishing builds.. The IJ scala plugin has channels.

Probably the intersection of bazel plugin users and IJ EAP users ain't big enough to make it worth your while. Thanks!

sorry, I'm just wondering should all the issues with tag "Fixed pending release" be closed? AFAIU the new version of the plugin released at 28Nov supports Idea 2018.3.

Yep, it's already released, closing.

The general IntelliJ plugin (https://plugins.jetbrains.com/plugin/8609-bazel) does support builds >= 183.* (i.e. 2018.3), whereas the CLion specific one (https://plugins.jetbrains.com/plugin/9554-bazel) does not, even though they seem to be the same release, at least they were released on the same day. Any idea why this is the case?

We don't support CLion 2018.3 yet. It generally lags behind IntelliJ because the plugin API changes a lot between releases, it tends to be generally less stable.

Thanks for the clarification! Is there a plan when support should be available? Or should I just subscribe to issue #457 and watch progress there?

Doesn't seem to work for 218.3.5 when trying to import gerrit:

Error:Cannot run program "bazel" (in directory "/Users/user/workspace/gerrit"): error=2, No such file or directory
Error:Could not run Bazel info

IntelliJ IDEA 2018.3.5 (Community Edition)
Build #IC-183.5912.21, built on February 26, 2019
JRE: 1.8.0_152-release-1343-b28 x86_64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
macOS 10.14.2

$ bazel version
Build label: 0.23.1
Build target: bazel-out/darwin-opt/bin/src/main/java/com/google/devtools/build/lib/bazel/BazelServer_deploy.jar
Build time: Mon Mar 4 10:40:32 2019 (1551696032)
Build timestamp: 1551696032
Build timestamp as int: 1551696032

Stacktrace:

java.util.concurrent.ExecutionException: com.google.idea.blaze.base.command.info.BlazeInfoException: blaze info failed with exit code: -1
    at com.google.common.util.concurrent.AbstractFuture.getDoneValue(AbstractFuture.java:526)
    at com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:507)
    at com.google.common.util.concurrent.AbstractFuture$TrustedFuture.get(AbstractFuture.java:83)
    at com.google.idea.blaze.base.async.FutureUtil$Builder.lambda$run$0(FutureUtil.java:96)
    at com.google.idea.blaze.base.scope.Scope.push(Scope.java:37)
    at com.google.idea.blaze.base.async.FutureUtil$Builder.run(FutureUtil.java:86)
    at com.google.idea.blaze.base.sync.BlazeSyncTask.doSyncProject(BlazeSyncTask.java:347)
    at com.google.idea.blaze.base.sync.BlazeSyncTask.syncProject(BlazeSyncTask.java:252)
    at com.google.idea.blaze.base.sync.BlazeSyncTask.lambda$run$0(BlazeSyncTask.java:211)
    at com.google.idea.blaze.base.scope.Scope.push(Scope.java:60)
    at com.google.idea.blaze.base.scope.Scope.root(Scope.java:52)
    at com.google.idea.blaze.base.sync.BlazeSyncTask.run(BlazeSyncTask.java:178)
    at com.google.idea.blaze.base.async.executor.ProgressiveTaskWithProgressIndicator.lambda$submitTask$0(ProgressiveTaskWithProgressIndicator.java:76)
    at com.google.idea.blaze.base.async.executor.ProgressiveTaskWithProgressIndicator.lambda$submitTaskWithResult$2(ProgressiveTaskWithProgressIndicator.java:110)
    at com.intellij.openapi.progress.impl.CoreProgressManager.lambda$runProcess$3(CoreProgressManager.java:180)
    at com.intellij.openapi.progress.impl.CoreProgressManager.lambda$runProcess$2(CoreProgressManager.java:164)
    at com.intellij.openapi.progress.impl.CoreProgressManager.registerIndicatorAndRun(CoreProgressManager.java:582)
    at com.intellij.openapi.progress.impl.CoreProgressManager.executeProcessUnderProgress(CoreProgressManager.java:532)
    at com.intellij.openapi.progress.impl.ProgressManagerImpl.executeProcessUnderProgress(ProgressManagerImpl.java:87)
    at com.intellij.openapi.progress.impl.CoreProgressManager.runProcess(CoreProgressManager.java:151)
    at com.intellij.openapi.progress.impl.CoreProgressManager.runProcess(CoreProgressManager.java:180)
    at com.google.idea.blaze.base.async.executor.ProgressiveTaskWithProgressIndicator.lambda$submitTaskWithResult$3(ProgressiveTaskWithProgressIndicator.java:110)
    at com.google.common.util.concurrent.TrustedListenableFutureTask$TrustedFutureInterruptibleTask.runInterruptibly(TrustedListenableFutureTask.java:125)
    at com.google.common.util.concurrent.InterruptibleTask.run(InterruptibleTask.java:57)
    at com.google.common.util.concurrent.TrustedListenableFutureTask.run(TrustedListenableFutureTask.java:78)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
    at java.lang.Thread.run(Thread.java:745)
Caused by: com.google.idea.blaze.base.command.info.BlazeInfoException: blaze info failed with exit code: -1
    at com.google.idea.blaze.base.command.info.BlazeInfoRunnerImpl.runBlazeInfo(BlazeInfoRunnerImpl.java:102)
    at com.google.idea.blaze.base.command.info.BlazeInfoRunnerImpl.lambda$runBlazeInfo$2(BlazeInfoRunnerImpl.java:72)
    ... 6 more

Works fine from command line and from IJ built in Terminal.

Fixed it by adding full path to bazel binary in IJ Settings -> Bazel Settings:
Bazel binary location: /usr/local/bin/bazel

Was this page helpful?
0 / 5 - 0 ratings

Related issues

davido picture davido  路  6Comments

lifeiteng picture lifeiteng  路  4Comments

brownry1986 picture brownry1986  路  8Comments

jschaf picture jschaf  路  4Comments

stevenleeS0ht picture stevenleeS0ht  路  7Comments