> -----Original Message----- > From: Trygve Laugstøl [mailto:[EMAIL PROTECTED] > Sent: Tuesday, November 30, 2004 9:40 AM > To: Maven Developers List > Subject: Re: versioning of maven-model drops >
[...] > > So I'm thinking we can always generate releases with > versioning in the > > package name and generate the versionless package name for > our use in > > maven-core. I guess that brings up the question of how to name the > > artifacts but that's the general notions. Once we figure this out I > > would like to cut a release of maven-model and let folks try it out. > > > > Thoughts? > > +1 for releasing it. > > So the SNAPSHOT version will be without versioned packages and the > released version will be with versions? > 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. --general comment-- I think that we are making this whole thing more complicated then it needs to be. 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. 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. 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) Note that POM is quite stable and the changes are going to be quite rare. This is not something which is going to change every week. 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). Everybody willing to be an early adopter of m2 when it is still in alpha stage should be prepered that things might not be stable and API and POM can change. And I think it is quite acceptable. 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 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. Michal --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
