action uses `graph` goal instead of `aggregate` for multi-module project?

[dbelyaev]

I am testing this action on my multi-module project and have noticed that the dependencies defined in the sub-modules are not being reported; they are missing from the dependencies output.

When I run the ferstl/depgraph-maven-plugin locally with the aggregate goal (instead of graph), it correctly outputs all dependencies from the parent pom.xml along with those from its sub-modules.

However, upon reviewing the code of the action, I found that it actually runs the graph goal within its aggregate function:

maven-dependency-submission-action/src/snapshot-generator.ts

Lines 78 to 83 in df268dd

	core.startGroup('depgraph-maven-plugin:aggregate');
	const mavenGraphArguments = [
	`com.github.ferstl:depgraph-maven-plugin:${DEPGRAPH_MAVEN_PLUGIN_VERSION}:graph`,
	'-DgraphFormat=json',
	`-DoutputFileName=${depgraphfilename}`,
	];

Is this behavior by design, or is the wrong goal being called?