Workaround for unnecessary scanning and indexing?
Answered
Every time I do a mvn build from a console, IntelliJ does a long scan and index when I switch back to it. In my mind this should not be happening since the only files that changed are in the excluded target directories. In fact, even a mvn clean will make IntelliJ rescan and index when it regains focus.
Anyone know of a workaround for this bug?
Please sign in to leave a comment.
Please file a bug at https://youtrack.jetbrains.com/issues/IDEA with the sample project to reproduce this problem. Excluded folders should not be indexed. There must be something specific about your project which triggers indexing (like generated sources).
I'm guessing it has something to do with a difference between how IntelliJ views external libraries versus how Maven views them.
Definitely no code generation in this project. I do notice this behavior in most of my multi module projects.