Re: Chicken and egg problem (disabling inheritance)

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

Re: Chicken and egg problem (disabling inheritance)

hello if I understand, you want something like this in the super pom build pluginManagement plugins plugin groupIdgroup ID/groupId artifactIdartifact ID/artifactId executions execution

Re: Chicken and egg problem (disabling inheritance)

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

Re: Chicken and egg problem (disabling inheritance)

FYI: the egg came first: http://www.cnn.com/2006/TECH/science/05/26/chicken.egg/index.html Thus, it's not really a chicken and egg problem. :-) Dan On Wednesday July 12 2006 2:38 pm, javaguy1974 wrote: Hello, I encountered the following problem (Maven 2.0.4): There is a top-level

Re: Chicken and egg problem (disabling inheritance)

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

Chicken and egg problem (disabling inheritance)

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

RE: Chicken and egg problem (disabling inheritance)

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

RE: Chicken and egg problem (disabling inheritance)

: javaguy1974 [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 12, 2006 1:38 PM To: users@maven.apache.org Subject: Chicken and egg problem (disabling inheritance) Hello, I encountered the following problem (Maven 2.0.4): There is a top-level (organizational) POM which is inherited by all other

RE: Chicken and egg problem (disabling inheritance)

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

Re: Chicken and egg problem (disabling inheritance)

On 7/13/06, javaguy1974 [EMAIL PROTECTED] wrote: 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