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: [email protected] 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 <plugins></plugins> 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]
