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 (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 bound to the package phase to log deployment info to the > database, thus it is declared in the top-level POM). Obviously, there is a > circular dependency which prevents me from installing/deploying the custom > plugin (mvn install; mvn deploy). I'm wondering if there is a way to > somehow disable plugin inheritance in the child POM (custom plugin POM). > (Custom plugin deployments don't need to be logged to the database). The > only thing I found that the parent POM can specify that a plugin won't be > inherited by a child POM but I'm looking for the opposite. I also tried to > use empty tag in the child POM but it didn't help. > > Thanks! > Lukasz -- J. Daniel Kulp Principal Engineer IONA P: 781-902-8727C: 508-380-7194 F:781-902-8001 [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Chicken and egg problem (disabling inheritance)
hello if I understand, you want something like this in the super pom group ID artifact ID deploy deploy record-build url user pass and in the child pom group ID artifact ID deploy On my side I use to specify the goal in the other pom too I 've also the case where the conf is in the child and in the super pom I really call plugins : super pom -> postprocess bytecode and call jar plugin (to get the job done in the right order or else the jar do not contain postprocess classes as the postprocess is made too late) child pom -> specify the conf of the postprocess (schema ) cordialement -- View this message in context: http://www.nabble.com/Chicken-and-egg-problem-%28disabling-inheritance%29-tf1932757.html#a5309547 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Chicken and egg problem (disabling inheritance)
So you're saying that I can use 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 relevant section from the top-level POM: group ID artifact ID deploy deploy record-build url user pass -- View this message in context: http://www.nabble.com/Chicken-and-egg-problem-%28disabling-inheritance%29-tf1932757.html#a5307643 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 actually mean by suggesting changing the plugin? Do you mean change the plugin POM so it no longer depends on the parent? This is exactly what I did by copying and pasting some settings from the parent but again that is not a desired solution. I believe what Mike is suggesting is that your top level pom does not need to depend upon your tracking pom, or your custom pom should not depend upon your top level pom. You need to break that dependency. You top level master pom should be providing default values for inheritance and not much else. For this I have an organisational wide bootstrap pom which does nothing more than define the internal repositories. Then each project inherits the bootstrap pom. In the project pom there is dependencyManagement, reporting, build, and pluginManagement which get inherited by the modules. I don't see it being such an issue that each project needs to define that it uses the custom plugin. You may be able to use the "inherited" tag in plugins/pluginManagement to do what you are wanting. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 mean change the plugin POM so it no longer depends on the parent? This is exactly what I did by copying and pasting some settings from the parent but again that is not a desired solution. -- View this message in context: http://www.nabble.com/Chicken-and-egg-problem-%28disabling-inheritance%29-tf1932757.html#a5297319 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Chicken and egg problem (disabling inheritance)
Change the plugin so that it does nothing when the current project uses pom and/or maven-plugin packaging? You have a circular dependency here - there's no solution other than breaking the cycle. You need to have a master POM which is not tracked via this plugin. -Original Message- From: 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 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 bound to the package phase to log deployment info to the database, thus it is declared in the top-level POM). Obviously, there is a circular dependency which prevents me from installing/deploying the custom plugin (mvn install; mvn deploy). I'm wondering if there is a way to somehow disable plugin inheritance in the child POM (custom plugin POM). (Custom plugin deployments don't need to be logged to the database). The only thing I found that the parent POM can specify that a plugin won't be inherited by a child POM but I'm looking for the opposite. I also tried to use empty tag in the child POM but it didn't help. Thanks! Lukasz -- View this message in context: http://www.nabble.com/Chicken-and-egg-problem-%28disabling-inheritance%2 9-tf1932757.html#a5294856 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Chicken and egg problem (disabling inheritance)
Use "pluginManagement" instead? -Original Message- From: javaguy1974 [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 12, 2006 1:50 PM To: users@maven.apache.org Subject: 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%2 9-tf1932757.html#a5295095 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 bound to the package phase to log deployment info to the database, thus it is declared in the top-level POM). Obviously, there is a circular dependency which prevents me from installing/deploying the custom plugin (mvn install; mvn deploy). I'm wondering if there is a way to somehow disable plugin inheritance in the child POM (custom plugin POM). (Custom plugin deployments don't need to be logged to the database). The only thing I found that the parent POM can specify that a plugin won't be inherited by a child POM but I'm looking for the opposite. I also tried to use empty tag in the child POM but it didn't help. Thanks! Lukasz -- View this message in context: http://www.nabble.com/Chicken-and-egg-problem-%28disabling-inheritance%29-tf1932757.html#a5294856 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
