Re: cvs commit: maven-components/maven-plugins/maven-surefire-plugin pom.xml

[Jason van Zyl <jv...@maven.org>]

On Tue, 2004-07-06 at 00:44, Emmanuel Venisse wrote:
> Why you do this? It's already define in parent pom.

It will be a stipulation to have the model version you want to use in
the POM so that in the future we can use methods to inspect the POM to
figure out what version it is so we can use the appropropriate versions
of the corresponding components to read the POM without having to
backtrack up the hierarchy.

For expedience and ease right now we are distinguishing between v3 and
v4 by the file name. We want better semantics for m2 so we have pom.xml
while m1 uses project.xml so that's easy to pick off, but when we move
to v4.x it won't be easy unless we have an easy way to distinguish which
will most likely mean reading a bit into the POM. I really hope that
when 2.0 final is released the POM will not need to change for a long
time but just so that this is easy the validator in place stipulates the
presence of modelVersion.

-- 
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 

Re: cvs commit: maven-components/maven-plugins/maven-surefire-plugin pom.xml

[Ben Walding <be...@walding.com>]

Isn't this what DTDs / System Identifiers are for?

I'm not necessarily saying that it should replace model version, but it 
seems to have a very similar purpose.

Cheers,

Ben

Jason van Zyl wrote:

>On Tue, 2004-07-06 at 00:44, Emmanuel Venisse wrote:
>  
>
>>Why you do this? It's already define in parent pom.
>>    
>>
>
>It will be a stipulation to have the model version you want to use in
>the POM so that in the future we can use methods to inspect the POM to
>figure out what version it is so we can use the appropropriate versions
>of the corresponding components to read the POM without having to
>backtrack up the hierarchy.
>
>For expedience and ease right now we are distinguishing between v3 and
>v4 by the file name. We want better semantics for m2 so we have pom.xml
>while m1 uses project.xml so that's easy to pick off, but when we move
>to v4.x it won't be easy unless we have an easy way to distinguish which
>will most likely mean reading a bit into the POM. I really hope that
>when 2.0 final is released the POM will not need to change for a long
>time but just so that this is easy the validator in place stipulates the
>presence of modelVersion.
>
>  
>