JBRes-7073: Add transformation for renaming methods

[dragoi75]

Changes

1. Moved Grazie and Koog dependencies from core to be main build.gradle.kts. See commit.
   → This was necessary to be able to send an LLM request from the java module.
2. Had to change how we close the project, see commit
   → Because Koog must be called with runBlocking, which requires coroutines, I had to add the dependency back, see here. But then I was once again getting a LinkageError. I think the issue is that IntelliJ 2025.1 and lower comes with an older version of coroutines. I tried changing to 2025.2 or newer, but that breaks the indexing in headless mode. And in the older version the limitedParallelism method does not exist, leading to an error.
3. Added the RenameMethodTransformation class:
   a. Finds all methods that meet the criteria (not a getter/setter/constructor, if it is part of an interface that implements from a library file, if the method overrides a different method, etc).
   b. Calls an LLM to find a substitute name (which is then checked for uniqueness).
   c. Renames all usages and references of the original method.

[github-actions]

Qodana Community for JVM

It 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 report

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

• Register at Qodana Cloud and configure the action
• Use GitHub Code Scanning with Qodana
• Host Qodana report at GitHub Pages
• 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]

• Or via our issue tracker: https://jb.gg/qodana-issue
• Or share your feedback: https://jb.gg/qodana-discussions

[Vladislav0Art]

Overall, good! 🎉

Left some comments. Highly suggest integrating them.

[Vladislav0Art]

[question; making sure] Is the order of parameters preserved? i.e., haveSameSignature(f1, f2) == false, with the f1 and f2 defined below.

fun f1(a: Int, b: String) {}

fun f2(b: String, a: Int) {}

[dragoi75]

I think so. The method's javadoc says: "Checks if the specified two PSI elements represent the same source element". From what I undestand, this means for f1 and f2 it would return false.

[Vladislav0Art]

[important] The implementation is nicely done! 👍🏻 and we can improve on this piece of code.

---

Proposal

You generate a single suggested name. What if you do, let's say, 10? or N?

I suggest making getNewMethodName generate a list of suggested names (parameterized by N), sorted by the most fitting first. Then, here, you'll iterate over each and try to apply.

In the prompt used in getNewMethodName, ask AI generate a list of N sorted name suggestions separated by a newline.

In general, it's better to implement all such suggestion-generating functions this way, instead of requesting a single suggestion over a single call.

---

Notes

1. You can add "${suggestedName}Internal" at the end of the generated list, so that you don't need an else-block.
2. null // Skip this method to avoid compilation errors - do not silently ignore the failure; log it instead. There is a HeadlessLogger just for that.

[dragoi75]

Great idea! Addressed in db03396.

[Vladislav0Art]

Should other Java default methods be mentioned here as well?

1. equals
2. hashCode
3. clone
4. wait / notify / notifyAll / finalize

[dragoi75]

Very good point! I though they should have @Override, which would filter them out before, but indeed it is not mandatory, so I added them in the filter.