marcelkliemannel / intellij-gradle-utilities-plugin Goto Github PK

If a Gradle version does not have a minor or patch version (e.g., 6.9), the command in the field "Update Gradle Wrapper" in the latest Gradle releases dialogs has a wrong version: ./gradlew wrapper --gradle-version=6.9.0.

Hi there, I just discovered your plugin and it's really great. Nice work.

I've been having an issue for a while now and I don't see Jetbrains getting to it (maybe ever), so I was wondering if we could do something about it here. It seems your plugin is well situated to add it.

I'm a maintainer of a lot (41) smallish Gradle projects that are interelated but I like to make sure they can build separately.

However, when running Gradle refresh, it runs them all simultaneously, which eventually fills up the RAM and locks up my computer. This is a blocker, because IntelliJ won't operate correctly if that doesn't happen successfully.
(https://youtrack.jetbrains.com/issue/IDEA-163751/Refresh-all-gradle-projects-action-should-limit-amount-of-simultaneous-processed-projects)

What do you think? Could we add a refresh button to this plugin that refreshes all the registered Gradle projects in order, but limiting the number of concurrent ones to some settable number? Usually, for instance, I'll let 5 go at a time and do this manually.

A feature request:

A highlighter for outdated dependencies would be nice, which you can update with a [ALT]-[ENTER] quick-fix

It's recommenced that the Gradle wrapper properties contain a property with the expected checksum of the Gradle wrapper JAR: https://docs.gradle.org/current/userguide/gradle_wrapper.html#configuring_checksum_verification

This should be checked in the "Verify Gradle Wrapper JAR and Distributions as well as in the Gradle environment overview.

This issue should improve the following two points:

• Show uptime of Gradle daemons.
• Provide a detailed description for collecting the statuses.

If there are no running Gradle daemons, it is still possible to open the context menu in the table:

This bug may also be in the daemons caches and Gradle distributions table.

The deletion of directories was disabled for testing and was not reenabled for the productive deployment.

Add a new action under the "Manage Gradle User Home" group to open the directory.

Currently, if an action is triggered from a dialog (e.g. collecting Gradle daemons), the action is started in the background. The action can't be canceled right now as long as the dialog is shown.

The actions from a dialog should be started as a modal task, so the built-in cancel action of IntelliJ tasks can be used.