[
https://issues.apache.org/jira/browse/LUCENE-10304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17457139#comment-17457139
]
Peter Gromov commented on LUCENE-10304:
---------------------------------------
It's certainly not my area of expertise, sorry :(
I've skimmed through some Gradle-related IntelliJ settings, but I've found
nothing dependency-scope-related. I guess the IDE tries to do everything
automatically here. AFAIK it runs Gradle and uses its OpenAPI to take the
project model built by it.
A ticket at https://youtrack.jetbrains.com/ could help.
> 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
>
> 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
