Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Luke Imhoff
    @KronicDeth
    Upgrading gradle 4.10.2 -> 5.3.1 fixed the problem
    Tobias Bouschen
    @tobous

    Hi @zolotov, I am running into an issue when trying to use the gradle-intellij-plugin with the option localPath to use a local IntelliJ installation. It fails with the following error when trying to load the gradle projects:

    org.gradle.api.ProjectConfigurationException: A problem occurred configuring project ':saros.intellij'.
    [...]
    Caused by: org.gradle.api.UncheckedIOException: Could not write to file '/usr/share/idea/ideaLocal-IC-191.6183.87-withKotlin.xml'.
    [...]
    Caused by: java.io.FileNotFoundException: /usr/share/idea/ideaLocal-IC-191.6183.87-withKotlin.xml (Permission denied)

    As the error messages already suggest, the build fails as it tries to create the config file in the IDE directory, which does not permit write actions.

    Is there a way to avoid this issue? Would writing the config file to a different directory (like the .IdeaIC20XX.X file that also stores other IDE settings) be a possibility?

    Alexander Zolotov
    @zolotov

    Is there a way to avoid this issue?

    chown or chmod? :)

    Would writing the config file to a different directory

    It complicates things, I don't really want the non-main approach of dependencies make the entire plugin more complicated

    Joshua Koehler
    @jjkoehler9_twitter
    I saw that 2019.1.2 was released. Tried to specify it as the 'version' but it couldn't be found in repositories. Is it a valid version to specify? Is there a wait period for when a new release comes out and when we can specify that new version in the plugin?
    Nthan
    @xingguang2013
    hi, how to view the debug information of the gradle refresh project in IDEA?
    Alexey Ivanov
    @iman89

    Hi! Not a long time ago I started to experience a strange error, could you please tell if this is only my problem?
    With version = 'IU-2019.1' in build.gradle I cannot build my plugin now:

    :buildSearchableOptions
    This build of IntelliJ IDEA has expired. Please download a new build from http://eap.jetbrains.com/idea2019
    :buildSearchableOptions FAILED
    
    FAILURE: Build failed with an exception.
    
    * What went wrong:
    Execution failed for task ':buildSearchableOptions'.
    > Process 'command 'C:\Users\Алексей\.gradle\caches\modules-2\files-2.1\com.jetbrains\jbre\jbrx-8u202-windows-x64-b1483.39\jre\bin\java.exe'' finished with non-zero exit value 7

    If I update to version = 'IU-2019.1.1' this error is resolved. However I would like to support my plugin starting from IU-2019.1 so I want to build it against that particular version.
    I have tried to clean gradle cache and re-download UI-2019.1 again but it didn't solve this problem.

    Alexander Zolotov
    @zolotov
    @jjkoehler9_twitter fixed
    @iman89 see the idea.log in build directory, it should contain the actual error. until then you can just disable that task
    Alexander Zolotov
    @zolotov
    image.png

    @xingguang2013 there is no good way to do this right now. you can add an error inside your build script (e.g. redundant '{') in order to see sync window ^

    then use Run with --debug option link

    Alexander Zolotov
    @zolotov
    @iman89 found the issue. it's fixed in 2019.1.2 only, sorry about that
    Nthan
    @xingguang2013
    @zolotov thanks
    Joshua Koehler
    @jjkoehler9_twitter
    @zolotov Thank you!
    Alexey Ivanov
    @iman89
    @zolotov Thanks! I'll probably disable buildSearchableOptions task. How will this affect the published plugin?
    Alexander Zolotov
    @zolotov
    @iman89 it won't contain index of searchable options in it, its settings won't be searchable
    td-ideabox
    @td-ideabox

    Hey folks, anyone know if there is a quick keymap to open the embedded terminal in a normal editor tab?

    <ALT>+<F12> opens the terminal in it's own special window, I'd like to open it as though it were another source file.

    Patrick Scheibe
    @halirutan
    @zolotov Currently, I don't specify a version in my Gradle file and it uses the latest EAP snapshot of the SDK. However, I always have to manually change the exact version for the markdown plugin. Is there a way to circumvent this and also simply use the latest plugin version from the JB repository?
    MrPossumsProgress
    @MrPossumsProgress
    Hi everyone. I am just following along with the plugin tutorial and am having trouble getting Gradle to find the IntelliJ open API or even present tools to me. Everything is configured on my machine correctly, my Gradle version is 5+ is and is OK according to its config panel . Is there a known issue with the directions here? https://www.jetbrains.org/intellij/sdk/docs/tutorials/build_system/prerequisites.htmlI posted here : https://intellij-support.jetbrains.com/hc/en-us/community/posts/360004184279-org-jetbrains-intellij-version-0-4-9-not-found-by-gradle at IJ forum also hopefully asking here soesn't count as cross posting ... thank you!
    Alexander Zolotov
    @zolotov
    @halirutan there is no way to do this and at the moment no intent to do it – I prefer users to have exact version of dependencies. Still, it might be improved in some way: JetBrains/gradle-intellij-plugin#282
    Patrick Scheibe
    @halirutan
    @zolotov That is OK. I just wanted to ensure that I don't miss something obvious.
    Etan Shaul
    @etanshaul
    we noticed that the publishPlugin task has recently deprecated use of password based authentication. specifically we are seeing this error:
    > Task :my-plugin:publishPlugin Password authentication for uploading is deprecated. Use token access instead: http://www.jetbrains.org/intellij/sdk/docs/plugin_repository/api/plugin_upload.html Failed to upload plugin: Authentication Failed: Invalid resource owner credentials
    Moreover, the gradle-intellij-plugin docs (https://github.com/JetBrains/gradle-intellij-plugin) still show using user / password for the publishPlugin task
    Is there any guidance on how to fix plugin publishing via the gradle-intellij-plugin
    Etan Shaul
    @etanshaul
    looks like publishPlugin has a token field, so it may be as easy as just using that
    Patrick Scheibe
    @halirutan
    @etanshaul I can give you a hand here, one second.
    @etanshaul I have the token inside my gradle.properties which are local and never shared in the repository (like you would do it with the password).
    Inside my build script (Kotlin DSL), I simply have
      named<org.jetbrains.intellij.tasks.PublishTask>("publishPlugin") {
        if (project.hasProperty("pluginsToken")) {
          token(project.property("pluginsToken"))
        }
    So inside my gradle.properties, I have pluginsToken = ...
    Patrick Scheibe
    @halirutan
    @etanshaul The token itself can be created when you log into your JB plugin page, then my profile, then Hub account and there you find Authentification.
    That's it.
    Etan Shaul
    @etanshaul
    great, thanks @halirutan ! This confirmed my understanding. I didn't notice that the publishPlugin task supports token based authentication. And yes definitely the token should never be committed / shared
    Jeff MAURY
    @jeffmaury
    I have 2 IJ plugins that uses the same API (which makes uses of the IJ platform). What is the recommanded way to build this common JAR ? Is it possible with the gradle plugin ?
    Colin Fleming
    @cmf
    Is it possible to disable the buildSearchableOptions task? It doesn’t work with my plugin, I get an error:
    org.picocontainer.defaults.UnsatisfiableDependenciesException: cursive.compiler.ClojureCompilerConfigurable has unsatisfied dependency: class cursive.compiler.ClojureCompilerSettings among unsatisfiable dependencies: [[class cursive.compiler.ClojureCompilerSettings, interface com.intellij.openapi.project.Project]] where DefaultPicoContainer (parent=DefaultPicoContainer (root)) was the leaf container being asked for dependencies.
    I manually create my searchable options anyway, so I don’t need this.
    Alexander Zolotov
    @zolotov
    @jeffmaury no recommended ways. create the common module, depend on it, profit
    @cmf you can disable it as any other task in Gradle
    Colin Fleming
    @cmf
    @zolotov Since that’s executed as a dependency of buildPlugin, would I have to modify the task graph?
    Alexander Zolotov
    @zolotov
    no
    Colin Fleming
    @cmf
    Great, thank you.
    Colin Fleming
    @cmf
    Ugh, I just realised what happened, I had searched in the repo for buildSearchableOptions but that doesn’t find the doc page because it refers to buildingSearchableOptions - sorry for the noise.
    Jeff MAURY
    @jeffmaury
    @zolotov should the common module be built by the gradle IJ plugin ?
    Alexander Zolotov
    @zolotov
    @cmf thanks, fixed
    @jeffmaury if you use anything from intellij sdk then you don't really have a choice – it should be built with gradle ij plugin but should not provide any plugin.xml
    Neerav Chauhan
    @adneerav

    Hello @all
    I am trying to create plugin for Android Studio
    As a beginner level I have just added on menu in Welcome screen as an AnAction
    and defined in plugin.xml

    <action id="com.hb.testplugin.NewProjectMenu" class="com.hb.testplugin.NewProjectMenu" text="Create New Custom Project">
          <add-to-group group-id="WelcomeScreen.QuickStart" anchor="first"/>
     </action>

    This things working if I run from intellij
    but when i Prepare plugin module from "Build" menu
    and if i install using jar in Android studio its not working

    Can anyone Help me in this ?

    Thanks

    Yann Cébron
    @YannCebron
    Neerav Chauhan
    @adneerav
    Oops sorry @YannCebron
    thanks for the link :)
    Joachim Beckers
    @jbeckers
    I'm trying to run the Plugin task using "Run with profiler" (JFR), but this does not work. I've filed https://youtrack.jetbrains.com/issue/IDEA-222512 If anyone knows of any way to make this work, please advise. Thanks!