No dependencies submitted when Maven outputDirectory set to a non-default value

[peter-murray]

If the POM utilizes a non-default outputDirectory the current execution of the dependency tree generation will use this non default location that the action will look for the results in.

Fetching the output directory setting will require dumping and parsing the effective POM which will add over head in the execution time. The depgraph-maven-plugin does have support for explicitly setting the output directory for the dependency tree files that are being parsed.

For a sensible interim (maybe long term fix) set the outputDirectory to target (the default maven setting, unless overridden) so as to provide a consistent place to fetch the dependency data from.

[peter-murray]

This was added in 3.0.3 to hard code the output directory to target when running the action