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" <[email protected]> wrote: > 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 dependency:list > depsFile.txt > cat depsFile.txt | grep "\[INFO\][^:]*:[^:]*:[^:]*:[^:]*:.*" | cut -d] -f2- > | sort -u > depsFileSorted.txt > > to get the unique sorted list, but again, i would have thought there would > be a direct way of doing this. > In the end, i would like to get the Dependency Management report of the > entire project (from the top container pom, like you said) on the generated > website. > That report does not produce the aggregate list of dependencies: i am not > sure what it produces, but that is not it. > > So i guess the question is how to get that aggregate report into the site > generation. > > With that txt file i create above i get by, but i wished its content got > generated automatically for me with the site and displayed in html like the > other reports. I am not quite sure why the maven site does not already do > that for the top container pom. > > Max > > > On Wed, Mar 12, 2014 at 1:16 PM, Curtis Rueden <[email protected]> wrote: > > > 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, 2014 at 4:31 PM, Max Calderoni <[email protected] > > >wrote: > > > > > 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 dependency plugin does is to list by module. For > our > > > release though, we are not interested in a per-module break-down, we > are > > > interested in the overall list of unique dependencies, and unique per > > GAV, > > > classifier, scope. > > > > > > The only thing i could find is this: > > > > http://grep.codeconsult.ch/2010/07/08/list-all-your-maven-dependencies/ > > > but, do i really have to use a script? is there some goal of some > plugin > > > out there that generates that or a better report for the entire > project's > > > dependencies for me? > > > The report generated in the Dependency Management section of the maven > > site > > > does it, but again, on a per-module basis. > > > Then the next question would be: how do i publish that in my maven > site? > > > > > > > > > -- > > > Max > > > > > > > > > -- > Max Calderoni >
