Brett Porter wrote: [...]
It's been decided writing small converters (and if the changes are compatible, they should be trivial to write) is better than trying to get the model to do some form of inheritence.
Minor versions might introduce deprecations on elements, for example - which makes the model different.
Is there any reason where this is actually going to cause you a problem?
I am just trying to propose something simpler as I am afraid that there will be way too many converters and parsers.
It could be that I don't get correctly what is the responsibility of "converter" in that solution.
Say that the latest POM version supported by m2 is v402 - how many packages with different model versions and how many converters we will need to distribute to support v400, v401?
I imagined that there will be always one parser in m2 for all possible released pom v4 variants and it will hide all the complexivity
related to changes in POM structure. Exactly like it used to be for m1 where for example we had dual support
for "id" and "groupId"/"artifactId' tags in dependency.
So if we will have something like maven2-model-v4-1.0.2.jar - it will contain the only parser which users/developers want to use
to parse all known variants of pom v4. Once we will have pom v403 we will release maven2-model-v4-1.0.3.jar
which support all previous versions and this new version. Isn't it simple enough?
Michal
---------------------------------------------------------------------- Nudzisz sie? Zagraj sobie! >>> http://link.interia.pl/f183d
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
