Re: versioning of maven-model drops

[Brett Porter]

I don't think that this is linked with snapshots.
Snapshot word in version is used for underlining the work in progress but
once the release is made it should be (almost) identical
to the last snapshot.
 

agreed.
--general comment--
I think that we are making this whole thing more complicated then it needs
to be.
 

Don't agree. It's actually quite simple as it is. Read on...
There are probably two issues related to numbering of pom versions:
At the moment we have two major versions of POMs: 3 and 4.
Those versions are incompatible. 

Then within major version we have (can have) minor versions like 4.0.0,
4.0.1 etc.
The changes introduced by minor version should be no breaking - it means
that we can possibly 
add new tags or deprecate tags but all existing tags should be supported.
 

agree to this.
Which means that in m2 which currently supports pom v4.0 we can simply put
POM model into o.a.m.model.v4.*
as this is not going to change anytime soon.
 

This is just a bit ugly, and does require an overhaul when you do a 
major version upgrade. Keeping "latest" in o.a.m.model.* works quite well.

The latest parser for each major version of POM should be able to parse all
sub-versions of that version (4.0.0. 4.0.1, 4.0.2)
 

This will still work - you should be able to drop in maven-model-4.0.1 
and it still works with code that expected 4.
Converters, which care more about any version differences, will need to 
access v400 and v401.

We should just not officialy release final version of POM v4.0.0 until we
are happy with all use cases which we want address in m2
(until we will reaach beta version).
 

This is exactly the plan.
I would also propose to re-think our numbering of POM versions and use the
following:
v3 - < maven 1.0.X
v4 - < maven 1.1.X   
v5 - < maven 2.0.X

 

I currently intend:
v3.1.0 - Maven 1.1: non breaking additions.
v4.0.0 - Maven 2.0: essentially starting from scratch, and transitive 
dependency enabled

For m1 we indeed need to generate model to o.a.m.project.* package.
The same model and parser for it can be generated to o.a.m.model.v3 and used
in m2, continuum etc.
 

exactly...
Cheers,
Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]