Intellij: Is it not working in the new IntelliJ 2018.2 for anyone else?

[Jdban]

7/25/18
11:14 AM    Required plugins weren't loaded
                Plugin 'Bazel' required for 'monorepo1' project is disabled.

I click Enable Bazel. Then:

11:18 AM    IDE and Plugin Updates: Restart IntelliJ IDEA to activate changes in plugins?

Restarting the IDE repeats the process

[plumpy]

We don't support 2018.2 yet.

[miramar-labs]

it's listed in build_defs.bzl though ..?
I tried installing from 2017.1 .. it doesn't show up in the jetbrains repo... then tried with 2018.2, still not showing up in the jetbrains repo ... tried building the source .. got errors ...
what's the trick to installing this?
is it supposed to work with 2017.1 ?

[plumpy]

2017.1 is too old. 2017.3 or 2018.1 will work.

[miramar-labs]

from the docs:
Our plugins are compatible with IntelliJ 2016.1.4 and later (full compatibity details are listed on the JetBrains plugin repository).

are you not sticking to that now?

[plumpy]

Oh, no, there were issues with the old versions of the plugins so we had to remove them from the repository. Now it's 2017.3 and later, sorry. I'll update the docs.

[miramar-labs]

ok so I switched to 2018.1 (OS X) and when I import our bazel project i'm seeing an IDE error:

com.google.idea.blaze.base.command.info.BlazeInfoException: blaze info failed with exit code: -1

any idea what that is?

[plumpy]

Most likely it can't find your bazel binary. Can you set the full path to the binary in Settings→Other Settings→Bazel Settings?

[miramar-labs]

that was the problem ..
one more question, what are the new compatible min/max intellij versions of other IDE's? (eg CLion)
thanks for the help!

[jcayzac]

Not showing up for me either in Android Studio 3.1.3 (based on 2017.3 I think).
Installing from disk fails, saying the plugin is not compatible.

[hsyed]

On the subject of android studio , older versions of android studio (3.0.3) paired with the recent plugins are unuseable. (Null pointer exceptions, src folders not being detected , sdk and jdk not being indexed).

The source code for these are not availble so the community cant contribute.

[brendandouglas]

You can find out exactly which versions are supported on the JetBrains plugin repo: https://plugins.jetbrains.com/

For the problems with AS 3.0, we haven't seen those kinds of issues internally, so I'm guessing you're using a version of the plugin not built against 3.0 (you can check on the website).

[hsyed]

@brendandouglas I got the tutorial building -- I used AS 3.0.1 (as suggested here) and installed the plugin from the plugin tab (2018.06.11.0.3). I have tried bazel 0.14.1 and 0.15.2.

shows up in the external libraries node.

Neither the JDK nor the Android SDK is indexed.

I cannot open the "project structure" view -- it either throws an NPE. Or it just doesn't open at all. So project structure likely doesn't have the SDK or JDK attached.

[hsyed]

I noticed JDK9 was chosen as the default in "external libraries". I opened the "default project structure" and provided the location of JDK8 this gets things indexing.

The "external libraries" still shows JDK9 though and I also still cannot open the project structure.

[jcayzac]

You can find out exactly which versions are supported on the JetBrains plugin repo: https://plugins.jetbrains.com/

For the problems with AS 3.0, we haven't seen those kinds of issues internally, so I'm guessing you're using a version of the plugin not built against 3.0 (you can check on the website).

I am not using AS 3.0 (that's old) but the current stable version, 3.1.3.

The latest version of https://plugins.jetbrains.com/plugin/9185-bazel says it's compatible with 171.4249—171.* but current version is 173.4819257 and loading the plugin fails.

Are you planning to keeping this plugin up to date, or does it only work with obsolete versions of Android Studio?

[brendandouglas]

There's some brief discussion on AS 3.1 in #278. We aren't planning to build the plugin against 3.1, but are skipping straight to 3.2 (the release we're currently dogfooding is built against 3.2).

[lupino3]

Will skipping to AS 3.2 make the plugin compatible with Intellij 2018.2? I had to revert to 2018.1 to get the Bazel plugin working, and am not proceeding with the update until the Bazel plugin is compatible with 2018.2. Thanks!

[brendandouglas]

The Android Studio and IntelliJ plugins are built and released separately. We'll be releasing against AS 3.2 before IntelliJ (or CLion) 2018.2.

[jspawar]

Is there any update on this? I'm a little confused by the closed PR above which was closed claiming support for building 2018.2 targets was already made by https://github.com/bazelbuild/intellij/pull/381 which appears to have been merged into master.

However, building with bazel build //ijwb:ijwb_bazel_zip --define=ij_product=intellij-2018.2 from current head of master produces a target that my macOS IntelliJ CE installation (version 182.3684.101) claims is still incompatible.

[miramar-labs]

yes, why was this closed? it still does not work on 2018.2 ...

[brendandouglas]

We're planning to move to 2018.2 in the release after next (3 weeks from now, scheduled to be uploaded on Friday September 14th).

At HEAD in this repo, intellij-2018.2 points to 2018.2.1 (182.3911.36), which is more recent than your version (182.3684.101). If you upgrade to the latest 2018.2, builds from HEAD should work.

We set the plugin XML 'since-build' field to the exact version we build against because the plugin API can change, even between dot releases.

[oswcab]

I was able to build the plugin from HEAD for latest IntelliJ (2018.2.2, aka, 182.4129.33) and it is working fine.

[cgruber]

at head, intellij-latest seems to be aliased to 2018.1. so --define=intellij-latest fails. However, --define=intellij-2018.2 does seem to work.

[nevion]

eagerly awaiting release of 2018.2 support, I've actually switched clion out as my IDE for the past 3 months, replacing with visual code while these 2018.2 related breakages happened; clion 2018.1 was having too many issues in the core IDE that were fixed in 2018.2 but then this plugin had support for that way out.

I just built and tested master and I get "IDE" errors when trying to sync the repository through the plugin, the IDE complains the plugin isn't loaded (even though it visually looks available), exact error is:

Error:Internal error: No SyncPlugin present which provides a default workspace type.

I also tested against the D8D8DDF3E27ABF305BC485BAEAFE48C9 branch which is much more recent, though I had to do the following to get it to build:

diff --git a/base/BUILD b/base/BUILD
index bc29551c..0c5058f2 100644
--- a/base/BUILD
+++ b/base/BUILD
@@ -18,7 +18,7 @@ java_library(
         "//proto:proto_deps",
         "//sdkcompat",
         "//third_party/auto_value",
-        "//third_party/java/error_prone:annotations",
+        "@error_prone_annotations//jar",
     ],
 )

[drichelson]

Is the next release scheduled? If so when might we expect it?

[ittaiz]

And will it mean 2018.1 won’t be supported?
On Wed, 26 Sep 2018 at 23:21 Dan Richelson [e-mail] wrote:

Is the next release scheduled? If so when might we expect it?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/bazelbuild/intellij/issues/375#issuecomment-424856352,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABUIFxFUkT9eQU0m3ctTr1wQiXQyJN64ks5ue-HKgaJpZM4VgkgX
.

[brendandouglas]

It's uploaded now for IntelliJ (and pending JetBrains approval for CLion and AS).

We only upload plugins for a single version, so 2018.1 won't get any updates. It's still supported though, typically for ~2 months (until we stop seeing major performance regressions in the new IDE version internally).

[miramar-labs]

we're on 2018.3 now....