On Sun, 2004-09-19 at 19:48, Brett Porter wrote:
> Hi,
>
> I've just been thinking about how we would go through the process of migrating
> from one version to the next of a model, and realised that we need to have each
> version extend the previous, instead of being cleanly generated.
No, we don't need to do that.
What is of utmost importance is binary compatibility in the case of
mojos that are coded against a specific version of maven. Subclassing
doesn't buy you anything in that regard: if you remove elements or
change signatures in the model it is irrelavent whether you subclass or
not. In addition it makes the tooling harder and I think would make
things more complicated. I believe a cleanly generated model with
adapter/converters is the approach to be taken.
I also hope that buy the time the final of m2 is release that the only
subsequent changes to the model will be additions to remain backward
compatible. I think after a sufficient length of time this will be
possible. If we find a dire case where we have really botched things up
then I would like to enact a policy of "correction by addition" where we
make a new element which serves the purpose we intend and deprecate the
incorrect element over a period of years. I am hoping this doesn't
happen, but it might and we can guarantee binary compatibility and
backward compatibility by following this policy.
Adding the notions of deprecation to modello is great, but I don't
support any of the other notions presented here.
>
> --
> jvz.
>
> Jason van Zyl
> jason@maven.org
> http://maven.apache.org
>
> happiness is like a butterfly: the more you chase it, the more it will
> elude you, but if you turn your attention to other things, it will come
> and sit softly on your shoulder ...
>
> -- Thoreau
|