Hi,
I'm using the dependency plugin a lot to copy stuff around (mostly to
get around the assembly plugin not allowing me to add arbitrary
artifacts to assemblies). Some uses are general, and are needed in
more than one module. AFAIK I should define these "general" executions
in a parent POM, under the <pluginManagement> section, and "call" them
from the actual modules by just specifying their execution ID, like:
<plugin>
<artifactId>maven-dependency-plugin</artifactId>
<executions>
<execution>
<id>unpack-all-swt</id>
</execution>
<execution>
<id>unpack-all-native</id>
</execution>
</executions>
</plugin>
However, the thing above does not only execute the "unpack-all-swt"
and "unpack-all-native" executions, but all other executions defined
in the parent POM. This also applies if I don't refer to executions
defined in parent at all, but define a new dependency plugin execution
in the child module.
It seems to me that if I "mention" a plugin in a child module, I get
all its executions defined in <pluginManagement> in the parent as
well. Is this as designed?
If this is the way it should work, is there a way to achieve what I
want? I.e. define some utility executions in parent that can be called
in child modules, but independent of other executions.
--
Regards,
Lóránt
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
