JAR command should spew out an automatic module name.

Looks like the problem is that it can't produce an automatic module out of it since it depends on the weld-environment-common. So until everything is modularized it is not possible to include it as a module dependency.

I managed to work around the issue by including the top-level dependency of weld-core instead, which contains both jars and therefore resolved both modules correctly.

TLDR: it is not possible to depend on weld-submodules that depend on each other right now.