Update docs with build changes (#8424)

Author: helin24

CONTRIBUTING.md

@@ -117,22 +117,6 @@ name and contact info to the [AUTHORS](AUTHORS) file.
     - [IntelliJ Downloads](https://www.jetbrains.com/idea/download/)
     - Either the community edition (free) or Ultimate will work.
 
-2. Create a `gradle.properties` file.
-   - In the root directory, create an empty `gradle.properties` file (`touch gradle.properties`)
-   - Add the following to the file:
-   ```
-   flutterPluginVersion=SNAPSHOT
-   ideaVersion=2024.3.1.7
-   dartPluginVersion= 243.21565.120
-   sinceBuild=243
-   untilBuild=253.*
-   javaVersion=21
-   kotlin.stdlib.default.dependency=false
-   org.gradle.parallel=true
-   org.gradle.jvmargs=-Xms1024m -Xmx4048m
-   ```
-    - **[Note]** If you want, you can manually change these properties to target different versions of IntelliJ. See `product-matrix.json` to find which configurations are supported.
-
 3. Start IntelliJ IDEA with the `flutter-intellij` project.
    - If you see a popup with "Gradle build scripts found",
      **confirm loading the Gradle project, and wait until syncing is done.**
@@ -188,13 +172,14 @@ name and contact info to the [AUTHORS](AUTHORS) file.
 
 5. Configure the modules for the Project
     - Select "Project Settings > Modules"
-    - Select the `flutter-intellij > flutter-idea` module
+    - Select the `flutter-intellij` module
     - Switch to the "Paths" window
     - Select the **Inherit project compile output path** option, then apply.
+    - Do the same for the subdirectories, `main` and `test`.
 
 6. Change the modules SDK to the Project SDK
     - Select "Project Settings > Modules"
-    - Select all the sub-directories under the `flutter-intellij > flutter-idea` module
+    - Select all the subdirectories under the `flutter-intellij` module
     - Switch to the "Dependencies" window
     - Change the "Module SDK" selection to `Project SDK`.
 
@@ -297,7 +282,7 @@ To be able to debug a single test class or test method, you need to do the follo
 The test configuration can be tricky due to the IntelliJ platform versioning.
 The plugin tool (below) can be a more reliable way to run tests.
 
-### Using the plugin tool on the command line
+### Using the command line
 
 To run unit tests on the command line:
 
@@ -322,31 +307,6 @@ Sometimes browsing the source code of IntelliJ helps understand platform details
   Accept all the root folders found by the IDE after scanning.
 - Do the same for the `intellij-plugins` repo to get Dart plugin sources. Sync to the same version as before.
 
-## Working with Android Studio
-
-Android Studio cannot use the Gradle-based project definition,
-so it still needs the `flutter-intellij-community.iml` file.
-Obviously, unit tests can only be run from the command line.
-
-1. Initialize Android Studio sources.
-2. Checkout Flutter plugin sources, tip of the tree.
-3. Follow the directions for setting up the Dart plugin sources in
-   `intellij-plugins/Dart/README.md` with these changes:
-    - you do not need to clone the intellij-community repo
-    - open studio-main/tools/adt/idea in IntelliJ
-    - possibly skip running `intellij-community/getPlugins.sh`
-4. Checkout Dart plugin sources.
-5. Using the Project Structure editor, import
-    - intellij-plugins/Dart/Dart-community.iml (if there are lots of errors, see step 7)
-    - flutter-intellij/flutter-intellij-community.iml
-6. Using the Project Structure editor, expand the tree to show `intellij > android > adt > ui`.
-   Select the `ui` module, then add a module dependency from it to `flutter-intellij-community`.
-   Also, add a dependency on the Dart module unless using step 7.
-7. (Optional, when Dart sources are not usable.) Make sure the `flutter-intellij-community` module
-   has a dependency on a library named `Dart`. It should be pre-defined, but if it is out of date,
-   then adjust it to point to `flutter-intellij/third_party/lib/dart-plugin/xxx.yyyy/Dart.jar`.
-   Delete the Dart module from the Project Structure modules list.
-
 ## Flutter DevTools Integration
 
 ### Working with Embedded DevTools (JxBrowser)

docs/Releasing.md

@@ -1,48 +1,14 @@
 # Creating a new release 
 
-## From IntelliJ:
-- ensure that the changelog in `CHANGELOG.md` is up-to-date (from the current milestone)
-  - edit `CHANGELOG.md` to update the release notes
-  - re-generate the plugin.xml files using `bin/plugin generate`
-  - commit these changes
-- create a new branch locally from that commit (`git checkout -B release_<version> SHA`, replacing `<version>` and `SHA` as appropriate)
-- in a terminal emulator, `bin/plugin --release=<version> build`, again replacing `<version>` with the current version number
-- the plugin is created as three separate `flutter-studio.zip` products in `/project/root/releases/release_<version>` (all three will be uploaded separately)
-  - 2017.3
-  - 2018.1
-- push your release branch upstream (`git push -u upstream release_21`)
-
-## From plugins.jetbrains.com:
-- sign into https://plugins.jetbrains.com
-- from https://plugins.jetbrains.com/plugin/9212?pr=idea, select `'update plugin'`
-- upload the `flutter-studio.zip` files (one for each product) created from the earlier step (note: the `.zip` file)
-
-# Pushing a patch to an existing release
-
-When it's necessary to patch a previously released build:
-
-## Change to the release branch
-
-- the fix should have already been committed to master
-- `git pull` to get the latest branch information
-- change to the branch for that release (`git checkout release_21`)
-
-## Cherry-pick the fix
-
-- cherrypick the specific commit (`git cherry-pick 2d8ac6a`)
-- ensure that the changelog in `resources/META-INF/plugin.xml` is up-to-date (from the current milestone)
-  - edit `CHANGELOG.md` to update the release notes
-  - again, to re-generate the plugin.xml files use `bin/plugin generate`
-- commit these changes
-- push your release branch upstream (`git push -u upstream release_21`)
-
-## Re-deploy the new Jar
-
-- in a terminal emulator, `bin/plugin --release=<version> build`, again replacing `<version>` with the current version number
-- the plugin is created as three separate `flutter-studio.zip` products in `/project/root/releases/release_<version>` (all three will be uploaded separately)
-  - 2017.3
-  - 2018.1
-  - 2018.2
-- sign into https://plugins.jetbrains.com
-- from https://plugins.jetbrains.com/plugin/9212?pr=idea, select `'update plugin'`
-- upload the `flutter-studio.zip` created from the earlier step (note: the `.zip` file)
+## Building the plugin zip file:
+- Make changes to the repository for the version.
+  - Edit `CHANGELOG.md` to include the current milestone and associated release notes.
+  - Increment the version for the dev release in `tool/kokoro/deploy.sh` (e.g. if the release about to go out is M90, the dev release version will be 91.0).
+  - Commit these changes.
+- Update `gradle.properties` with the release number.
+- Run `./gradlew buildPlugin` - this will generate a `flutter-intellij.zip` file in `build/distributions`.
+
+## Uploading the plugin:
+- Sign in to https://plugins.jetbrains.com.
+- From https://plugins.jetbrains.com/plugin/9212?pr=idea, select `'update plugin'`.
+- Upload the `flutter-intellij.zip` file created from the earlier step (note: the `.zip` file).

docs/building.md

@@ -3,8 +3,6 @@
 Update the `gradle.properties` file
 
 - IntelliJ IDEA versions can be found here: https://www.jetbrains.com/idea/download/other.html
-    - Version numbers for the `product-matrix.json` should be taken from the name of the downloaded file, not versions listed on the
-      website.
 - Dart Plugin versions can be found here: https://plugins.jetbrains.com/plugin/6351-dart
 - Android Studio versions can be found
   here: https://developer.android.com/studio/archive & https://plugins.jetbrains.com/docs/intellij/android-studio-releases-list.html
@@ -32,7 +30,7 @@ invited to the organization to upload plugin files.
 Building for releases was formerly done by the `plugin` tool when we wanted to run a script to generate multiple release versions at once.
 See [tool/plugin/README.md](../tool/plugin/README.md) for details.
 
-The `plugin` tool is being retained currently for the dev build, linting, and verifying the plugin.
+The `plugin` tool is being retained currently for deploying the dev build, linting, and generating live templates.
 
 ### install gs_util
 

resources/liveTemplates/readme.md

@@ -21,3 +21,5 @@ To re-generate the flutter_miscellaneous.xml template file, run:
 ```
 ./bin/plugin generate
 ```
+
+Commit these at the time of making changes to live templates.