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.
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
Hi Max,
You could create a module (in the same build or outside of it) with pom
packaging and which depends on all the modules of your build. Then when you
list its dependencies, you'll get them all (excluding non-transitive ones
such as optional scope deps).
Regards,
Curtis
On Mon, Mar 10,
Hi Curtis,
thanks for answering. Yes, that was the first thing i tried, like you said,
i had done:
cd topPomDir
mvn dependency:list
but that does not print out the same nice report that i see in the
Dependency Management section of the generated site, which is what i want.
So, i did:
mvn
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
--
Sent from my mobile
On Mar 13, 2014 12:24 AM, Max Calderoni max.calder...@gmail.com wrote:
Hi Curtis,
thanks for answering. Yes, that
Hi,
was not able to find a quick way to list a consolidated list of all
dependencies in your project.
What i am looking for is something along the lines of dependency:list, or
dependency:resolve of the maven dependency plugin, but for the entire
multi-module project.
What i see the maven
