At the moment, Moditect simply uses MavenProject.getArtifacts to determine the module path to use when invoking jdeps to create module-info. While this is generally correct behavior, there are situations when it would be useful to be able to explicitly exclude some dependencies from the module path.

For example, when generating module-info for a module that shades one or more internal dependencies without relocation, not excluding the shaded dependencies from the module path leads to superfluous "split packages" warnings, as the same classes/packages exist in both artifacts. Excluding shaded dependency eliminates those warnings.