ok..., based on my previous email, trying re-asking here the same question from a different angle:
The project-info-reports:dependency-management goal is used to generate the Project DependencyManagement report. In in a multi-module project, is it currently already possible to generate the same report (maybe off of the main pom project container of your entire source tree), which aggregates all the reports of all submodules (unique GAV+scope entries)? On Fri, Mar 14, 2014 at 10:15 AM, Max Calderoni <max.calder...@gmail.com>wrote: > Hello Mirko, > > it's an idea. This that you describe in particular i cannot do, because it > will break containment (has implications with site generation, build, etc), > but i had tried a similar hack, by creating a dummy jar project that was > depending on every single module in the entire source tree. > > It almost worked, but not quite, because other than being problematic > remembering to always add every module as a dependency to the dummy module > , both test and not, dependency:list will shrink a dependency to one scope > only. That is, it will not show that dependency A is used as 'compile' > somewhere and somewhere else as 'test', while we want to see that in a > report. > > Seems to me that this problem cannot be resolved with the dependency > plugin alone, because dependencies can only be found by running the entire > tree: the container pom project will run as first in the reactor build > order, not as last. > > Seems more of a problem for a reporting plugin, like for example the Maven > Project Info Reports Plugin. > > I am going to ask a different question based on that, see if i can get an > answer. > > Cheers, > > Max > > > On Wed, Mar 12, 2014 at 10:34 PM, Mirko Friedenhagen < > mfriedenha...@gmail.com> wrote: > >> Hello Max, >> >> what about switching this to a jar project without sources (maybe a >> readme >> txt as resource), which is not deployed or installed? >> >> Regards >> Mirko >> >> -- Max Calderoni
