gradle-intellij-plugin | Gradle plugin for building plugins for IntelliJ-based IDEs | Plugin library

 by   JetBrains Kotlin Version: v1.14.1 License: Apache-2.0

kandi X-RAY | gradle-intellij-plugin Summary

kandi X-RAY | gradle-intellij-plugin Summary

gradle-intellij-plugin is a Kotlin library typically used in Plugin, Gradle applications. gradle-intellij-plugin has no bugs, it has no vulnerabilities, it has a Permissive License and it has medium support. You can download it from GitHub.

Gradle plugin for building plugins for IntelliJ-based IDEs
Support
    Quality
      Security
        License
          Reuse

            kandi-support Support

              gradle-intellij-plugin has a medium active ecosystem.
              It has 1320 star(s) with 275 fork(s). There are 75 watchers for this library.
              OutlinedDot
              It had no major release in the last 12 months.
              There are 74 open issues and 728 have been closed. On average issues are closed in 280 days. There are 5 open pull requests and 0 closed requests.
              It has a neutral sentiment in the developer community.
              The latest version of gradle-intellij-plugin is v1.14.1

            kandi-Quality Quality

              gradle-intellij-plugin has 0 bugs and 0 code smells.

            kandi-Security Security

              gradle-intellij-plugin has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
              gradle-intellij-plugin code analysis shows 0 unresolved vulnerabilities.
              There are 0 security hotspots that need review.

            kandi-License License

              gradle-intellij-plugin is licensed under the Apache-2.0 License. This license is Permissive.
              Permissive licenses have the least restrictions, and you can use them in most projects.

            kandi-Reuse Reuse

              gradle-intellij-plugin releases are available to install and integrate.
              Installation instructions, examples and code snippets are available.
              It has 14910 lines of code, 465 functions and 75 files.
              It has medium code complexity. Code complexity directly impacts maintainability of the code.

            Top functions reviewed by kandi - BETA

            kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
            Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of gradle-intellij-plugin
            Get all kandi verified functions for this library.

            gradle-intellij-plugin Key Features

            No Key Features are available at this moment for gradle-intellij-plugin.

            gradle-intellij-plugin Examples and Code Snippets

            No Code Snippets are available at this moment for gradle-intellij-plugin.

            Community Discussions

            QUESTION

            Intellij Idea - Android Studio Plugin - Build Failed
            Asked 2021-Aug-05 at 09:37

            from 5 months ago I use Intellij Idea CE to develop an android studio plugin

            but

            after Android studio latest update

            ...

            ANSWER

            Answered 2021-Aug-05 at 09:37

            As gradle-intellij-plugin doesn't support Android Studio natively, it doesn't know what compiler version should be used for local AS SDK, and it tries to compiler with the same version as AS, which does not exist. To fix that, you need to specify a particular compiler version explicitly using instrumenting dsl.

            All available versions are listed in intellij maven repository. In your case, I think 203.7717.56 would be just fine.

            So the configuration should look like this:

            Source https://stackoverflow.com/questions/68655763

            QUESTION

            Build Intellij plugin in IDEA 2019.1 & 2020.3
            Asked 2020-Dec-19 at 18:00

            Building for IDEA 2019.1 works like a charm! I thought that building for 2020.3 would be just a matter of pointing to 2020.3 installation folder and that's it, but it is not being even close to it.

            That's my gradle.build

            ...

            ANSWER

            Answered 2020-Dec-19 at 18:00

            it turns out there was a missing plugin dependency.

            this line was not being effective to resolve such dependency. In order to fix that I had to remove apply plugin: 'java' and set intellij.plugin

            Source https://stackoverflow.com/questions/65322223

            QUESTION

            Using IntelliJ 2019.3.1 for plugin development for Clion. How to add c++ language support for my plugin project?
            Asked 2020-Jan-12 at 09:12

            I am currently learning about writing plugins for IntelliJ IDEs. I am especially interested in developing plugins for CLion. Therefore I would like to add support for c++ to my plugin project.

            My problem:

            I read in the documentation how to develop plugins for c++.However the way it is described does not work for me. IntelliJ cannot resolve the dependency I want to add.

            What I currently know:

            1. This part of the documentation explains that plugins may depend on other plugins, and how to add dependencies.

            Plugin dependencies

            Your plugin may depend on classes from other plugins. In this case, plugins can be either bundled, third-party or even your own. For instructions on how to express the dependencies, refer to Plugin Dependencies.

            Your plugin should specify which product or products it will be compatible with (all IntelliJ-based IDEs, CLion only, or some subset). You can do that by declaring module dependencies with the tag in plugin.xml (see Plugin Compatibility with IntelliJ Products).

            2. This part of the documentation explains which functionality is in which plugin. Each specific language seems to be a plugin. So developing a plugin which wants to parse c++, will depend on the c++ plugin.

            Modules Specific to Functionality More specialized functionality is also delivered via modules and plugins in IntelliJ Platform-based products. For example, the com.intellij.modules.python module supports the Python language-specific functionality. If a plugin uses functionality from this module, such as Python-specific inspections and refactoring, it must declare a dependency on this module.

            ...

            The following table lists(1) modules or built-in plugins that provide specific functionality, and the products that currently ship with them.

            According to the table mentioned above I need to add com.intellij.modules.cidr.lang as dependency for c++. However when I add this line to my plugins.xml file the cidr.lang part is not recognized.

            3. In this Stackoverflow question, which is about java plugin development, someone answered that there was recently a change, that one now also has to add the needed plugins to build.gradle. Furthermore there was a change tha java language support is now a buildin plugin.

            My guess what todo

            I guess c++ support is now also a buildin plugin? But how can I add it?

            So instead of

            ...

            ANSWER

            Answered 2020-Jan-12 at 09:12

            I found the answer in the documentation. I just had to reimport the project.

            Exploring Module and Plugin APIs

            Once the dependency on a module or plugin is declared in plugin.xml, it’s useful to explore the packages and classes available in that dependency. The section below gives some recommended procedures for discovering what’s available in a module or plugin on which a project depends. These procedures assume a project has the build.gradle and plugin.xml dependencies configured correctly. Exploring APIs as a Consumer

            Exploring the available packages and classes in a plugin or module utilizes features in the IntelliJ IDEA IDE.

            If the project is not up to date, Reimport the Gradle project as a first step. Reimporting the project will automatically update the dependencies.

            So for c++ language support there is no need to add something to build.gradle

            My plugin.xml

            Source https://stackoverflow.com/questions/59690209

            Community Discussions, Code Snippets contain sources that include Stack Exchange Network

            Vulnerabilities

            No vulnerabilities reported

            Install gradle-intellij-plugin

            TIP Create new plugins with a preconfigured project scaffold and CI using IntelliJ Platform Plugin Template. Here is the manual on how to start developing plugins for the IntelliJ Platform using Gradle. Also, please take a look at the FAQ.
            The following attributes are a part of the Setup DSL intellij { ... } in which allows you to set up the environment and dependencies.
            Value may have IC-, IU-, CL-, PY-, PC-, RD-, GO- or JPS- prefix in order to define IDE distribution type.
            intellij.version and intellij.localPath should not be specified at the same time.
            version #'2017.2.5' or 'IC-2017.2.5'
            build #'172.4343' or 'IU-172.4343'
            'LATEST-EAP-SNAPSHOT'
            'IC' - IntelliJ IDEA Community Edition.
            'IU' - IntelliJ IDEA Ultimate Edition.
            'CL' - CLion.
            'PY' - PyCharm Professional Edition.
            'PC' - PyCharm Community Edition.
            'RD' - Rider.
            'GO' - GoLand.
            'JPS' - JPS-only.
            intellij.version and intellij.localPath should not be specified at the same time.
            For plugins from the JetBrains Plugin Repository use format pluginId:version.
            For bundled plugins version should be omitted: e.g. org.intellij.groovy for IDEA/plugins/Groovy plugin.
            For sub-projects use project reference project(':subproject').
            If you need to refer plugin's classes from your project, you also have to define a dependency in your plugin.xml.
            org.plugin.id:version[@channel]'org.intellij.plugins.markdown:8.5.0', 'org.intellij.scala:2017.2.638@nightly'
            bundledPluginName'android', 'Groovy'
            project(':projectName')project(':plugin-subproject')
            If true then user-defined values from patchPluginXml.sinceBuild and patchPluginXml.untilBuild will be used (or their default values if none set).
            Is useful for building plugins against EAP IDE builds.
            If true then the user-defined value from patchPluginXml.sinceBuild (or its default value) will be used as a since and an "open" until value.
            If patchPluginXml.untilBuild has a value set, then sameSinceUntilBuild is ignored.
            Since sources are not needed while testing on CI, you can set it to false for a particular environment.
            Empty value means the Gradle cache directory will be used.

            Support

            You can debug the source code of gradle-intellij-plugin (e.g. put breakpoints there) if you add a reference to your local copy into settings.gradle of your IntelliJ plugin:.
            Find more information at:

            Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items

            Find more libraries
            CLONE
          • HTTPS

            https://github.com/JetBrains/gradle-intellij-plugin.git

          • CLI

            gh repo clone JetBrains/gradle-intellij-plugin

          • sshUrl

            git@github.com:JetBrains/gradle-intellij-plugin.git

          • Stay Updated

            Subscribe to our newsletter for trending solutions and developer bootcamps

            Agree to Sign up and Terms & Conditions

            Share this Page

            share link