glad to know I'm not the only one! I think it's not OK though. Running tests in IDE is super useful, especially for debugging, but also for visualizing coverage. I think there must be a bug; we do say:
11:15 $ ./gradlew helpIDEs > Task :helpIDEs IntelliJ IDEA ============= Importing the project as a gradle project should just run out of the box. On Thu, Jun 2, 2022 at 11:11 AM Tomoko Uchida <[email protected]> wrote: > > Hi Mike, > I also can't run the tests in lucene/core.tests with IntelliJ IDEA, > but it should be able to run with the plain gradle command from a > console. > ./gradlew -p lucene/core.tests/ test > > I'm not sure the exact cause of that though IDEs' java module support > looks far from perfect for now, I would recommend not to use IDE when > running modular tests... > > Tomoko > > 2022年6月2日(木) 23:44 Michael Sokolov <[email protected]>: > > > > In IntelliJ building Lucene main branch I see this: > > > > .../workspace/lucene/lucene/core.tests/src/test/module-info.java:23: > > error: module not found: org.apache.lucene.core.tests.main > > requires org.apache.lucene.core.tests.main; > > ^ > > > > Am I doing it wrong? Does anybody else encounter this? I tried > > re-importing the Gradle model, which succeeds, but then when I build > > the project I get the above error. > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
