Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix unresolved imports with IntelliJ 2024.1+ #4193

Merged
merged 2 commits into from
Oct 7, 2024

Conversation

vga91
Copy link
Collaborator

@vga91 vga91 commented Sep 18, 2024

With newer versions of IntelliJ (from 2024.1.x),
the imports of other java classes in extended are not properly detected without this fix.

See the Slack discussion: https://neo4j.slack.com/archives/C136J23GE/p1723459229156629


EDIT:
Added another commit, since a similar problem occurs in extended-it module,
that is, we cannot import classes, if they are from the moduleextended, in another package name.

Therefore, without the change committed,

testImplementation project(':extended').sourceSets.main.allJava

we cannot e.g. import JdbcUtil (coming from package apoc.load.util) into class `` (package apoc.load),
even if this line is present:

implementation project(":extended")

@vga91 vga91 force-pushed the fix-unresolved-imports-with-newest-intellij branch from bbd4a04 to 7d2087b Compare October 4, 2024 09:58
@RobertoSannino RobertoSannino merged commit 65cc9b7 into dev Oct 7, 2024
5 checks passed
@RobertoSannino RobertoSannino deleted the fix-unresolved-imports-with-newest-intellij branch October 7, 2024 08:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants