Plugin projects targeting AppCode can be developed using IntelliJ IDEA with the Gradle IntelliJ Plugin (1.x).
With the release of AppCode 2022.3, we're sunsetting the product. Please see this blog post for details.
Configuring Plugin Projects Targeting AppCodeWhen targeting 2020.3, please see this migration guide.
The Gradle configuration of AppCode plugin projects uses neither Product-Specific nor IntelliJ IDEA Attributes. Instead, configure AppCode plugin projects to use the intellij.localPath attribute.
AppCode plugin development requires installing AppCode locally.
The table below summarizes the Gradle IntelliJ Plugin (1.x) attributes to set in the plugin project's Gradle build script. Click on an entry in the table's Attribute column to go to the documentation about that attribute.
gradle-intellij-plugin Attribute
Attribute Value
Path to locally installed target version of AppCode. For example, for macOS:
/Users/$USERNAME$/Library/Application Support/JetBrains/Toolbox/apps/AppCode/ch-0/193.5662.55/AppCode.app/Contents.
Path to locally installed target version of AppCode. For example, for macOS:
/Users/$USERNAME$/Library/Application Support/JetBrains/Toolbox/apps/AppCode/ch-0/193.5662.55/AppCode.app/Contents.
The dependency on the AppCode APIs must be declared in the plugin.xml file. As described in Modules Specific to Functionality table, the <depends> tags must declare com.intellij.modules.appcode module dependency, or com.intellij.appcode plugin dependency for plugins targeting only versions 2020.3+.
See AppCode Extension Point and Listener List for the complete list.
Use the Exploring APIs as a Consumer process to identify the libraries in AppCode. Test your plugin with any version of AppCode you wish to support.
19 March 2025
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4