next#580
Conversation
When a new project has no releases yet, `gh api repos/{owner}/{repo}/releases`
returns empty JSON, causing `xargs` to fail with exit code 123:
"unexpected end of JSON input".
use xargs -r instead of explicit empty check for draft cleanup
…onfiguration from `build.gradle.kts`
…om `build.gradle.kts`
…from `build.gradle.kts`
…eference from `build.gradle.kts` and updating `gradle.properties`.
… `pluginVersion` configuration from `build.gradle.kts`
…build.gradle.kts` as it is already set in the `plugin.xml`
Qodana Community for JVMIt seems all right 👌 No new problems were found according to the checks applied 💡 Qodana analysis was run in the pull request mode: only the changed files were checked View the detailed Qodana reportTo be able to view the detailed Qodana report, you can either:
To get - name: 'Qodana Scan'
uses: JetBrains/qodana-action@v2025.1.1
with:
upload-result: trueContact Qodana teamContact us at qodana-support@jetbrains.com
|
…dle.properties`.
…ions.toml`, redundant since IntelliJ Platform 251+
…e` with `group` and `version` in `gradle.properties`, and update diff filtering in workflow.
…rapper should be updated with `./gradlew wrapper --gradle-version=9.4.1 && ./gradlew wrapper`
…d.gradle.kts` and `gradle.properties`.
…le.kts` for cleaner configuration.
… from `libs.versions.toml`.
…ts for simplified dependency management.
There was a problem hiding this comment.
Wow... that's certainly unexpected...
Why is that? It was convenient, after all
There was a problem hiding this comment.
Thanks for questioning that, Danil. Let me explain the background story first:
We're moving toward the multi-module setup, which requires and/or makes setup easier when utilizing the settings.gradle.kts. This makes you define the org.jetbrains.intellij.platform.settings version there, and not Gradle Version Catalog. We end up with Gradle plugin versions defined in multiple places.
Thanks to the pluginManagement.plugins, we can manage versions from one place.
That'll leave us with Version Catalog storing only library versions, not the IntelliJ Platform! Sure, we can define there just the IntelliJ Platform version, but accessing it as a string isn't obvious. That's why it was defined in gradle.properties — again, multiple sources of truth.
If we summarize, we can define versions in gradle.properties, gradle/libs.versions.toml, build.gradle.kts, and settings.gradle.kts.
That's a pretty overcomplicated state for a Template project, isn't it?
3 participants
No description provided.