On 13/02/2008, at 7:15 PM, Mark Struberg wrote:
Does the refactoring of the XML give us any new functionality
besides only 'looking better'?
No, but it seems that's reason enough :) The technical underpinnings
do give the value of being able to add things to the model now,
however, and still parse old POMs effectively.
And what is the price we pay? Getting non-compatible with existing
poms? Someone already mentioned
the forward compatibility once 'new' poms get their way into the
repos. There are still many
companies working with mvn 2.0.4 and lower, which will need the old
poms in the public repos.
Do we need own public repos then? If so, this would be more the kind
of maven-3.0 then.
The repos thing is fine - we just keep publishing the same format as
before. It's not really read by humans there. All versions of Maven
will continue to interoperate - until you start hitting projects that
require Maven 2.1 to build (but that is to be expected, and it doesn't
force anyone to upgrade for their own projects).
Altough I agree that the attributes would have been better if we got
them in 4.0.0 format, i also
admit that it's imho simply too late.
With regard to the familiarity issue - I don't believe this is a
problem, as long as it is evolution (so, we are migrating towards one
solution, not allowing it to change on a project-by-project basis).
HTH,
Brett
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
