[
https://issues.apache.org/jira/browse/LUCENE-10304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17466348#comment-17466348
]
Dawid Weiss commented on LUCENE-10304:
--------------------------------------
Uwe noticed that Eclipse has a problem with module-info.java files - once you
open them with a Java editor, they cause havoc and build errors, even if the
file is originally excluded from compilation by classpath settings.
Workaround 1: disable automatic compilation, edit in java editor, then clean
and refresh the project, returning the module-info nodes to "excluded" state.
Workaround 2: use plain text editor, not Java editor, to edit those files.
!screenshot-1.png!
I've no idea how this can be fixed or if it can be fixed at all from our side.
> 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
