[
https://issues.apache.org/jira/browse/LUCENE-10304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17485692#comment-17485692
]
Chris Hegarty commented on LUCENE-10304:
----------------------------------------
Linking an IDEA issue here since it has the same underlying cause (IDEA does
not expose enough low-level configuration to allow to put dependencies on the
module-path or class-path), see https://youtrack.jetbrains.com/issue/IDEA-286436
> Make sure IDEs are usable after modules are introduced
> ------------------------------------------------------
>
> Key: LUCENE-10304
> URL: https://issues.apache.org/jira/browse/LUCENE-10304
> Project: Lucene - Core
> Issue Type: Sub-task
> Reporter: Dawid Weiss
> Priority: Major
> Attachments: screenshot-1.png
>
>
> IntelliJ IDEA imports everything in 'runtime' scope after jms PR. I didn't
> look inside but intellij seems to look at (or parse?) the classpath from
> javaCompile - if it doesn't see a module/jar there, it considers it a runtime
> dependency.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
