I have a common-sense idea (possibly wrong) of what the plugin element's "inherited" child element does, but I was hoping for a very clear explanation.
I'm sure I'm just looking in the wrong place, but I didn't see anything in the POM reference that explains what the inherited element does. I am sure that it must govern whether a plugin's configuration is passed on down to sub-poms that inherit from the pom inside of which the relevant plugin declaration is found. But can it also prevent the plugin stanza itself from being inherited? I have a multi-module project set up with a root pom that is both an aggregator and a parent. (I know, I know, let's leave that one alone for now.) I'd like to set up a plugin declaration to use the maven-assembly-plugin to put together a kind of standalone uber-distribution from the root. But I don't want this plugin--any aspect of it, at all--to be inherited by the children. That is, when I run mvn assembly:single from the root, I want it to run only once, and not to run for the child projects. Perhaps this is impossible. Perhaps this is possible only with mvn -N assembly:single from the root. Any tips are gratefully (as always) appreciated. Best, Laird
