Tim O'Brien wrote:
People will use whatever implementation they feel like using. I'd
propose that you start by shipping Maven with two:
1. Classic - the way it works now
2. Reduced XML - the thing that Nicolas proposed
If someone wants to ship an implementation that understands something
like:
http://www.coderoshi.com/2007/08/maven-less-ugly.html
If people start using it, and there is a demand to add native support
for someone's format, then you can add it in later.
As long as it contains the same info, no more, no less, than the POM
you have now. What's the damage? Does Eric's YAML break the
Universal Understanding, or does it provide another path for users who
might not want to start at XML even if it is different?
I wish it was that simple. There are hundreds of pre-existing poms that
you would need to be able to read, so it isn't just a case of use one or
the other. In a best case scenario you would need to use your "new"
parser for the new format and the "classic" for the old. Now if folks
start creating poms using all kinds of syntax the situation will quickly
get out of hand. To me, making this pluggable is a recipe for disaster.
Ralph
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
