Thanks Benjamin, I respect your points about the scope of use. Need to digest it some.
Benjamin wrote: >Lee Wrote: >> Maybe we need a plugin-parent that mojo-parent inherits from? >Personally I don't see the need for this. I would rather like to see Non-Mojo developers to start off with a minimal POM and copy over only those bits that they need, after learning and understanding the POM, instead of blindly inheriting from a POM that is tailored to somebody else. Maven-archetype-plugin adds no project infrastructure (site, reports, definition of plugin versions, etc). Sounds like you wouldn't even be in favor of adding this to maven-archetype-plugin? ________________________________ From: Benjamin Bentmann <[email protected]> To: [email protected] Sent: Tue, December 1, 2009 12:45:53 PM Subject: Re: [mojo-dev] [VOTE] Release Mojo Parent POM 23 Lee Thompson wrote: > I think mojo-parent is the best definition of which plugins are current and > working in the <pluginmanagement> section of the POM and a good place to > start for project reporting in the <reporting> section. With the addition of > the no repositories rule, aren't I restricted from inheriting from > mojo-parent to develop a non-mojo plugin for a company and publishing to an > internal repo? This is the Mojo parent, not the world parent. The Mojo parent is meant to serve the Mojo community (as its corporate parent), and only the Mojo community. We define extensions, plugins and their executions in there that serve our specific environment and requirements. That some of those bits work in other contexts as well is by incident and not by design. > Case in point, several people have asked me how to write a maven plugin and I > tell them just inherit from mojo-parent and overload the mailing lists, jira, > and repo definitions. This won't work anymore and the starting point in > playing around would be to copy paste what you want out of mojo-parent. > Duplication is Evil... ... misuse as well and IMHO this is misuse of a corporate parent that is meant to serve only a particular organization/community. In other words, I don't see an obligation on the Mojo side to support external development with our parent. > Maybe we need a plugin-parent that mojo-parent inherits from? Personally I don't see the need for this. I would rather like to see Non-Mojo developers to start off with a minimal POM and copy over only those bits that they need, after learning and understanding the POM, instead of blindly inheriting from a POM that is tailored to somebody else. Benjamin --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
