On 10/12/06, Stephen Colebourne <[EMAIL PROTECTED]> wrote:
Can you summarise in a paragraph why we need a publicly published POM for those of us maven luddites who haven't followed the discussion, so we know what is being voted on and why?
Think of the POM as a project configuration, it's a single file. Maven 2 supports the concept of a POM hierarchy: There is an (officially released) Apache POM (see http://repo1.maven.org/maven2/org/apache/apache/ ), which configures the things that are common for all Apache projects (license, organization, for example). There might be a Jakarta specific POM, which extends the Apache POM, a Commons proper POM and finally the project specific POM, for example commons-fileupload. Currently there is only a SNAPSHOT POM for commons proper: In other words, a release of commons-fileupload can only choose to ignore the hierarchy and derive from the Apache POM directly or it can wait for an official release of the commons-proper POM, it's natural parent. The latter is what we vote about. Does that help? Jochen -- My wife Mary and I have been married for forty-seven years and not once have we had an argument serious enough to consider divorce; murder, yes, but divorce, never. (Jack Benny) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
