OK with some grepping I I found these module names in various places (looks like they were defined as maven module names, where I guess maybe it is best practice for every submodule's name to contain the complete hierarchy of all its ancestor modules??)
./gradlew lucene:lucene-analyzers:lucene-analyzers-nori:test seems to work but ./gradlew lucene:lucene-analyzers:test 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]
