Don't show conflicts and duplicates in aggregated graph.
This does not make sense because dependencies are resolved individually
for each module in the reactor. As a result, the same dependency edge in
the graph could once occur as conflict, once as duplicate and once as
resolved dependency.

Example:
Suppose, we have two modules "module-1" and "module-2" in the reactor.
module-2 has a dependency to module-1 and both modules have a dependency
to the third-party library "commons-wtf". module-1 references version
3.0 of this library and module-2 references version 3.1. If we now would
display conflicts in the aggregated graph, we would get these edges
(amongst others):

module-1 --- 3.1 (included) ---> commons-wtf  (perspective of module-1)
module-1 --- 3.1 (conflict) ---> commons-wtf  (perspective of module-2)
module-2 --- 3.0 (included) ---> commons-wtf  (perspective of module-2)

Such a graph is not useful whatsoever. Unless it is not possible to
access all resolved dependencies within the whole reactor, we cannot
show duplicates and conflicts.
No need to require direct invocation
Renamings (part 1)
Renamings (part 2)
Add <skipErrorNoDescriptorsFound> to maven-plugin-plugin configuration
Generate plugin documentation
Add some project info reports to the site
Add ceremonial POM stuff
Test source folder
Add license stuff