模块系统不区分生产代码和测试代码，所以如果你选择模块化测试代码， prod.module 和 test.module 不能共享相同的包 com.acme.project ，如 specs ：

The module system does not distinguish between production code and test code, so if you choose to modularize test code, the prod.module and the test.module cannot share the same package com.acme.project, as described in the specs:

无干扰 - Java编译器，虚拟机和运行时系统必须确保包含相同名称包的模块不会相互干扰。如果两个不同的模块包含相同名称的包，那么从每个模块的角度来看，该包中的所有类型和成员仅由该模块定义。一个模块中该包中的代码必须无法访问另一个模块中该包中的包私有类型或成员。

Non-interference — The Java compiler, virtual machine, and run-time system must ensure that modules that contain packages of the same name do not interfere with each other. If two distinct modules contain packages of the same name then, from the perspective of each module, all of the types and members in that package are defined only by that module. Code in that package in one module must not be able to access package-private types or members in that package in the other module.

如Alan Bateman所示，Maven编译器插件使用 --patch-module和模块系统在编译src / test / java树中的代码时提供的其他选项，以便使用测试类扩充测试中的模块。在运行测试类时，这也是由Surefire插件完成的（请参阅支持运行单元测试命名为Java 9模块）。这意味着您无需将测试代码放在模块中。

As indicated by Alan Bateman, the Maven compiler plugin uses --patch-module and other options provided by the module system when compiling code in the src/test/java tree, so that the module under test is augmented with the test classes. And this is also done by the Surefire plugin when running the test classes (see Support running unit tests in named Java 9 modules). This means you don't need to place your test code in a module.