So you're saying that I can use pluginManagement to declare a plugin and
all its parameters in the parent but really instantiate it in child POMs?
Can you provide an example? My concern is that I don't want to redefine the
plugin and all its settings (parameters) in child POMs. Thanks.
Here is a
I doesn't work for me either (Maven 2.0.4). Moreover, the site directories
are structured based on the POM iheritance, which is probably not intended.
I have the following hierarchy of parent POMS:
top-level-pom
parent-ear-pom
parent-web-pom
My multi-module project is structured this
OK, thanks for explaining this to me!
--
View this message in context:
http://www.nabble.com/Chicken-and-egg-problem-%28disabling-inheritance%29-tf1932757.html#a5310059
Sent from the Maven - Users forum at Nabble.com.
-
To
Actually, the only solution that I found is to merge top-level POM
(excluding the plugin) to the child POM and not inherit from the top-level
POM.
--
View this message in context:
http://www.nabble.com/Chicken-and-egg-problem-%28disabling-inheritance%29-tf1932757.html#a5295095
Sent from the
Hello,
I encountered the following problem (Maven 2.0.4):
There is a top-level (organizational) POM which is inherited by all other
projects' POMs. Particularly, a custom Maven plugin inherits from the
top-level POM. The problem is that the top-level POM uses the custom plugin
(the plugin is
Well, this is still not what I'm looking for. This would require to redeclare
the plugin in many child POMs which inherit from the top-level one (30+).
--
View this message in context:
http://www.nabble.com/Chicken-and-egg-problem-%28disabling-inheritance%29-tf1932757.html#a5295755
Sent from
It would be nice if Maven provided a capability for a child POM to ignore
some inherited stuff like plugins. Otherwise, it is very difficult to design
a truly top-level organizational POM that is shared by all projects. I'm not
sure what you actually mean by suggesting changing the plugin? Do you
