You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
guava-testlib should have an Automatic-Module-Name for use in dependent modular projects. It seems that its module name, guava.testlib is derived from the filename as of 30.1.1.-jre. Issue #2920 and related issues only added a module name for Guava itself.
While guava-testlib is most frequently used as a test-scoped dependency, there are cases where one may need to refer to its module name. Testing on the module path is possible. Sometimes this is necessary for IDE compatibility, as in ben-manes/caffeine#540
The text was updated successfully, but these errors were encountered:
guava-testlib should have an Automatic-Module-Name for use in dependent modular projects. It seems that its module name,
guava.testlib
is derived from the filename as of 30.1.1.-jre. Issue #2920 and related issues only added a module name for Guava itself.While guava-testlib is most frequently used as a test-scoped dependency, there are cases where one may need to refer to its module name. Testing on the module path is possible. Sometimes this is necessary for IDE compatibility, as in ben-manes/caffeine#540
The text was updated successfully, but these errors were encountered: