Multi-module maven projects might define a project key at the top-level which is used for all modules.
This MR allows the MvnProjectAnalyzer to inspect the parent project's pom for a project key (recursively).
Currently only works for multi-module maven projects which are part of the same repository. A future enhancement would be to download/calculate the effective pom for the maven project so that property inheritance actually works (my employer actually uses this along with some interpolated property variables... which is another thing that the effective model would help with).
Multi-module maven projects might define a project key at the top-level which is used for all modules.
This MR allows the MvnProjectAnalyzer to inspect the parent project's pom for a project key (recursively).
Currently only works for multi-module maven projects which are part of the same repository. A future enhancement would be to download/calculate the effective pom for the maven project so that property inheritance actually works (my employer actually uses this along with some interpolated property variables... which is another thing that the effective model would help with).