Skip to content

impl: support for unlimited 'Until Build' setting #549

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 9 commits into
base: main
Choose a base branch
from

Conversation

fioan89
Copy link
Collaborator

@fioan89 fioan89 commented May 5, 2025

Every time a new GW version is released we need to change the untilBuild setting. With latest IntelliJ Platform Plugin we can provide unlimited upper range with no manual intervention each time a new release is happening.

IntelliJ Platform Gradle Plugin 2.x is the build system that supersedes the Gradle IntelliJ Plugin 1.x, and this is the version that comes with the ability to provide unlimited until build support.

This is a major overhaul of the DSL, I've tested these changes locally with GW 2023.3 (the minimum supported version), and I've also compared the plugin.xml with a previous version to make sure it is generated correctly.

fioan89 added 3 commits May 6, 2025 01:00
This upgrade is needed in order to be able to upgrade the gateway/intellij
platform plugins.
This is needed in order to be able to specify "unlimited until builds".
IntelliJ Platform Gradle Plugin 2.x is the build system that supersedes
the Gradle IntelliJ Plugin 1.x, and this is the version that comes with
the ability to provide unlimited until build support.

This is a major overhaul of the DSL, I've tested these changes locally with
GW 2023.3 (the minimum supported version), and I've also compared the plugin.xml
with a previous version to make sure it is generated correctly.
Every time a new GW version is released we need to change the untilBuild setting.
With latest IntelliJ Platform Plugin we can provide unlimited upper range with no
manual intervention each time a new release is happening.
Copy link
Member

@matifali matifali left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, although the PR does more than just make the until version unlimited. It may be better to extract the refactoring to another PR.

@fioan89
Copy link
Collaborator Author

fioan89 commented May 5, 2025

It is a valid point, my thinking was that they could go in one shot because the upgrade to Platform plugin 2.x is mandatory.

Use gateway DSL to provide the platform type and version.
The plugin verification as well as the platform type depends on the versions in the format "2025.x"
fioan89 added 5 commits June 19, 2025 22:47
We don't have any UI tests but the test task still fails because it misses junit 4 dependencies.
For the unit tests we use kotlin tests library with junit 5 as a backend.
listProductsReleases was renamed to printProductsReleases in version 2.x
Copy link
Contributor

github-actions bot commented Jun 19, 2025

Qodana Community for JVM

23 new problems were found

Inspection name Severity Problems
Usage of API marked for removal 🔴 Failure 13
Local 'var' is never modified and can be declared as 'val' 🔶 Warning 1
Incorrect string capitalization 🔶 Warning 1
Constant conditions 🔶 Warning 1
Usage of redundant or deprecated syntax or deprecated symbols 🔶 Warning 1
Redundant nullable return type 🔶 Warning 1
String concatenation that can be converted to string template ◽️ Notice 2
Argument could be converted to 'Set' to improve performance ◽️ Notice 1
Class member can have 'private' visibility ◽️ Notice 1
Redundant lambda arrow ◽️ Notice 1

💡 Qodana analysis was run in the pull request mode: only the changed files were checked

View the detailed Qodana report

To be able to view the detailed Qodana report, you can either:

  1. Register at Qodana Cloud and configure the action
  2. Use GitHub Code Scanning with Qodana
  3. Host Qodana report at GitHub Pages
  4. Inspect and use qodana.sarif.json (see the Qodana SARIF format for details)

To get *.log files or any other Qodana artifacts, run the action with upload-result option set to true,
so that the action will upload the files as the job artifacts:

      - name: 'Qodana Scan'
        uses: JetBrains/[email protected]
        with:
          upload-result: true
Contact Qodana team

Contact us at [email protected]

@fioan89 fioan89 requested review from f0ssel and matifali June 19, 2025 21:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants