> By the way, the > classpath problems seem to occur with either method (gradle or > intellij) when running entire suite - I just confused while switching > back and forth. This is on main, haven't tried 9x recently >
Some of these headaches are caused by Lucene's folder structure and have been there forever - resources mixed with source classes. I don't know if you can make intellij use a folder as a resource and as source directory at the same time - I don't think it's possible. If so, tests that rely on these resources will fail. It's been this way since I remember - nothing has changed here. There is also a lot of trickery involving modular paths etc. I don't think it'll be easy to simulate this in Intellij. Then, 99% of test cases will run just fine from intellij without any special hacks (I think)... I'd say - run individual tests from intellij, add a test launching config redirecting to gradle for the whole suite - it should also be faster this way since tests will run in parallel between modules. D.
