[
https://issues.apache.org/jira/browse/HDDS-16001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated HDDS-16001:
----------------------------------
Labels: pull-request-available (was: )
> Intellij run configrations are invalid
> ---------------------------------------
>
> Key: HDDS-16001
> URL: https://issues.apache.org/jira/browse/HDDS-16001
> Project: Apache Ozone
> Issue Type: Bug
> Reporter: Rishabh Patel
> Assignee: Rishabh Patel
> Priority: Major
> Labels: pull-request-available
> Attachments: Screenshot 2026-07-27 at 1.36.11 PM.png,
> image-2026-07-27-13-36-45-301.png, image-2026-07-27-13-37-16-170.png,
> image-2026-07-27-13-37-34-893.png
>
>
> The run configurations in Intellij are invalid. This can be seen from the
> little red cross marks on the run configurations. The error says that the
> class in the run configuration doesn't exist in the class path.
> !image-2026-07-27-13-37-34-893.png!
>
> !image-2026-07-27-13-37-16-170.png!
>
> !image-2026-07-27-13-36-45-301.png!
>
> Since Intellij 2025.1 release, the way Intellij processes pom files has
> changed. It creates separate .main and .test modules in Maven projects.
> See
> [https://youtrack.jetbrains.com/projects/IDEA/issues/IDEA-371535/Confusing-separate-.main-and-.test-modules-in-Maven-projects]
> If there is a difference between your main and test configurations, then
> Intellij will create separate main and test modules. As such the default
> classpath won't work. The run configurations are pointing to classes which
> are not in the default classpath but instead in the classpath with the .main
> suffix.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
