Your understanding is incorrect, Michael. This:
> ./gradlew lucene:lucene-analyzers:lucene-analyzers-nori:test seems to work runs task 'test' inside module lucene:lucene-analyzers:lucene-analyzers-nori while this: > ./gradlew lucene:lucene-analyzers:test tries to run task 'test' in module lucene:lucene-analyzers but this project doesn't have this task at all. Try pointing at a folder instead of fully qualified project name (benefit of the shell expanding paths as well): ./gradlew -p lucene/analysis test the difference being it'll try to run the 'test' task in any of the submodules under that folder. Also, this will show you all available tasks and projects: gradlew tasks --all Dawid > > does not. it would really be nice to have a way to run all the analysis tests > > On Thu, Nov 14, 2019 at 8:05 AM Michael Sokolov <[email protected]> wrote: > > > > I'm trying to run the tests in the lucene/analysis module (really I'd > > like to run tests in lucene/analysis/kuromoji), but I'm having trouble > > figuring out the naming convention and/or the project structure. It > > doesn't seem to be the same as the directory structure? EG I am able > > to run tests in core with: > > > > ./gradlew lucene:lucene-core:test > > > > although I expected it to be > > > > ./gradlew lucene:core:test > > > > I forget how I stumbled on the "correct" naming > > > > but none of these work: > > > > ./gradlew lucene:analysis:test > > ./gradlew lucene:lucene-analysis:test > > ./gradlew lucene:analyzers:test > > ./gradlew lucene:lucene-analyzers:test > > > > (gradle suggested the "lucene-analyzers" project name) > > > > where is the mapping from module to gradle project name kept? Can we > > make it consistent with the directory naming, and ideally not have an > > explicit mapping at all? > > --------------------------------------------------------------------- > 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]
