modulepath vs/ classpath when no module-info file and main() is provided by a dependency

I'm still seeing similar symptoms of https://youtrack.jetbrains.com/issue/IDEA-187390 which is marked as fixed. Specifically I have an application that doesn't have a module-info file and a run configuration that tries to run a main() from a dependency (which also doesn't have a module-info file).  IntelliJ is running with all dependencies added to the modulepath instead of the classpath, which breaks because one of the dependencies (unrelated to the main()) has a malformed module-info definition.

The referenced workaround ("As a workaround, you may create a simple main class in project sources which invokes the desired one") works to run on the classpath as desired, but seems like it shouldn't be needed per the 2018 comments?  Is there another way to force running on the classpath?  If this is still a bug, should I comment on the above youtrack or file a new one?