Cannot Generate SQL File from DAO Located in a Source Directory Created via Gradle Source Set

[xterao]

Describe the bug
When attempting to generate an SQL file from a DAO method located in a source directory created via a Gradle source set configuration, a quick-fix action results in an IOException.

After restarting the IDE, SQL file generation and navigation between files work correctly without any issues.

Stack Trace:

2025-07-01 09:43:48,698 [83358483] SEVERE - #c.i.o.u.ObjectTree - java.io.IOException: Invalid file name: 'D:'
com.intellij.util.IncorrectOperationException: java.io.IOException: Invalid file name: 'D:'
	at org.domaframework.doma.intellij.common.psi.PsiDaoMethod.generateSqlFile$lambda$8$lambda$7(PsiDaoMethod.kt:189)
	at com.intellij.openapi.command.WriteCommandAction.lambda$runWriteCommandAction$4(WriteCommandAction.java:341)
	at com.intellij.openapi.command.WriteCommandAction$BuilderImpl.lambda$doRunWriteCommandAction$1(WriteCommandAction.java:147)
	at com.intellij.openapi.application.impl.AnyThreadWriteThreadingSupport.runWriteAction$lambda$5(AnyThreadWriteThreadingSupport.kt:379)
	at com.intellij.openapi.application.impl.AnyThreadWriteThreadingSupport.runWriteAction(AnyThreadWriteThreadingSupport.kt:389)
	at com.intellij.openapi.application.impl.AnyThreadWriteThreadingSupport.runWriteAction(AnyThreadWriteThreadingSupport.kt:379)
	at com.intellij.openapi.application.impl.ApplicationImpl.runWriteAction(ApplicationImpl.java:896)
	at com.intellij.openapi.command.WriteCommandAction$BuilderImpl.lambda$doRunWriteCommandAction$2(WriteCommandAction.java:145)
	at com.intellij.openapi.command.impl.CoreCommandProcessor.executeCommand(CoreCommandProcessor.java:217)
	at com.intellij.openapi.command.impl.CoreCommandProcessor.executeCommand(CoreCommandProcessor.java:188)
	at com.intellij.openapi.command.WriteCommandAction$BuilderImpl.doRunWriteCommandAction(WriteCommandAction.java:154)
	at com.intellij.openapi.command.WriteCommandAction$BuilderImpl.run(WriteCommandAction.java:121)
	at com.intellij.openapi.command.WriteCommandAction.runWriteCommandAction(WriteCommandAction.java:341)
	at com.intellij.openapi.command.WriteCommandAction.runWriteCommandAction(WriteCommandAction.java:329)
	at org.domaframework.doma.intellij.common.psi.PsiDaoMethod.generateSqlFile$lambda$8(PsiDaoMethod.kt:185)
	at com.intellij.openapi.application.impl.AnyThreadWriteThreadingSupport.runReadAction$lambda$3(AnyThreadWriteThreadingSupport.kt:258)
	at com.intellij.openapi.application.impl.AnyThreadWriteThreadingSupport.runReadAction(AnyThreadWriteThreadingSupport.kt:272)
	at com.intellij.openapi.application.impl.AnyThreadWriteThreadingSupport.runReadAction(AnyThreadWriteThreadingSupport.kt:258)
	at com.intellij.openapi.application.impl.ApplicationImpl.runReadAction(ApplicationImpl.java:853)
	at org.domaframework.doma.intellij.common.psi.PsiDaoMethod.generateSqlFile(PsiDaoMethod.kt:174)
	at org.domaframework.doma.intellij.inspection.dao.quickfix.GenerateSqlQuickFix.applyFix(GenerateSqlQuickFix.kt:40)
	at org.domaframework.doma.intellij.inspection.dao.quickfix.GenerateSqlQuickFix.applyFix(GenerateSqlQuickFix.kt:28)

To Reproduce

1. A source directory is created using a Gradle source set (e.g., src/custom/java).
2. A DAO is placed within this directory.
3. Running the quick-fix to generate an SQL file from a DAO method causes the IDE to fail with an I/O error due to malformed path construction.

Expected behavior
The relative path should be correctly resolved even when the source directory is defined via a Gradle source set, and SQL file generation should complete without error.

Screenshots

Desktop :

• IDEA Version [2024.1.7]
• Doma Tools Version [1.1.0]

Additional context
Add any other context about the problem here.

[xterao]

Cause
The process that constructs the relative path for the SQL file generation attempts to remove the module path from the DAO file path. However, paths created through Gradle source sets do not include the module path string retrieved from module settings.

doma-tools-for-intellij/src/main/kotlin/org/domaframework/doma/intellij/common/dao/DaoMethodUtil.kt

Line 221 in cb8f87f

.replaceFirst(pathParams.moduleBasePath?.path ?: "", "")

As a result, the absolute path remains unchanged and invalid. When this path is used in subsequent steps, an incorrect path string such as:

resources/D:\~~~

is generated, leading to an IOException.

[xterao]

Root Cause: Incorrect Timing and Source of Module Directory Resolution

The problem stemmed from both where the module directory structure was first generated and when that structure was resolved.

---

Example Source Directory Structure Within a Module

- common/java
- main/java
- build/generate/~~~~/java/main

---

Original Behavior

• The logic for resolving source directories originally considered only the first entry returned for a module (excluding build directories).
• The directory structure was cached using the module object as the key, meaning that all files within the same subproject (module) would share the same base path.

Problem Scenario

• After launching IntelliJ IDEA, if the first opened file is under main/java, the base path is cached as main/java.
• If a new source set (e.g., common/java) is later added and a DAO from common/java is opened, it still uses the cached main/java as the module base path.
• This causes the SQL relative path to be constructed incorrectly.

The reverse scenario produces the same issue:

• If the user first opens a DAO under common/java, then later opens one under main/java, the base path remains common/java.
• As a result, generating SQL or jumping between files based on a main/java DAO also leads to an incorrect relative path, producing an IOException.

---

Solution

• Instead of relying on only the first entry, loop through all source root entories retrieved from the module manager.
• Explicitly exclude build directories during the loop.
• Maintain a list of all valid module base paths.
• When resolving a DAO's SQL file path, use the module base path that matches a substring within the DAO file path.

This ensures that:

• Regardless of the file opening order,
• And as long as the source directories are correctly structured,
• A valid base path will always be found for generating a correct SQL file relative path.

---

This change makes the resolution mechanism more robust and consistent across multiple source sets in the same module.