Igor, > On 1 Jun 2017, at 04:32, Igor Ignatyev <igor.ignat...@oracle.com> wrote: > > Hi Felix, > > I have suggested the exact opposite change[1-3] to fix the same problem.
I’m sorry, but this is all just too confusing. After your change, who, or what, is responsible for building/compiling the test library dependencies? Test library code has no @modules tags, so does not explicitly declare its module dependencies. Instead module dependencies, required by test library code, are declared in the test using the library. If we wildcard, or otherwise leave broad build dependencies, from tests then there is no way to know what new module dependencies may be added in the future. That is, one of, the reason(s) I asked Felix to be explicit about the build dependencies. -Chris. > [1] https://bugs.openjdk.java.net/browse/JDK-8181391 > [2] http://mail.openjdk.java.net/pipermail/core-libs-dev/2017-June/048012.html > [3] http://cr.openjdk.java.net/~iignatyev//8181391/webrev.00/index.html
