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 <plugins></plugins> tag in the child POM but it didn't help. > > Thanks! > Lukasz -- J. Daniel Kulp Principal Engineer IONA P: 781-902-8727 C: 508-380-7194 F:781-902-8001 [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
