If they are runtime scoped dependencies then you don't reference them from the "source" so there is no need to merge their javadoc in...
That could be a justification for such a treatment... not that I am saying it is the way things should be, just a potential explanation. On 27 August 2013 22:35, Laird Nelson <[email protected]> wrote: > I have an .ear file that I build using Maven. I rely on the > maven-javadoc-plugin's jar goal to build javadoc for me. > > I use the includeTransitiveDependencies property to allow my .ear project > to be fully javadoced: all the stuff that it depends on has -sources.jars > and my intent is to have the plugin process them. > > Left to my own devices, I'd declare most of my dependencies in this project > as <scope>runtime</scope>. I notice that when I do this, the javadoc > plugin runs and effectively does nothing. > > Is it intentional that the includeTransitiveDependencies property only > "works on" compile-scope dependencies? > > Thank you, > Best, > Laird > > -- > http://about.me/lairdnelson >
