2

According to What does "Required filename-based automodules detected." warning mean? Maven warns about projects that depend upon automatic modules (libraries whose module name is derived from their filename).

  1. How are we supposed to figure out which dependency is triggering this error?
  2. Do we need to worry about transitive dependencies or only immediate dependencies?

For example, the latest version of Guava defines Automatic-Module-Name but its dependencies do not. Consequently, should projects that requires Guava avoid publishing to Maven Central?

Update: Filed https://issues.apache.org/jira/browse/MCOMPILER-366

Gili
  • 86,244
  • 97
  • 390
  • 689
  • 1. Does `jdeps --list-deps` help in what you're looking for? 2. Shouldn't worry about transitive dependencies(maven) unless they are used in your module(java). – Naman Dec 06 '18 at 06:07
  • @nullpointer `jdeps --list-deps` lists the modules I `requires` but it does not tell me which ones are automatic modules. Also building up the `module-path` of dependencies manually is not fun at all :) – Gili Dec 06 '18 at 14:12
  • Yes, that's what I was suspecting as well. Let's wait for figuring out how is `maven-compiler-plugin` intervening with ModuleResolution to figure out what all are automatic modules. – Naman Dec 06 '18 at 14:27

0 Answers0