-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 30, 2004 7:11 PM
To: Maven Developers List
Subject: Re: versioning of maven-model drops
On Wed, 2004-12-01 at 00:27, Michal Maczka wrote:
Brett Porter wrote:
I am just trying
Not sure what that means. It's easy now to change the name of package.
...
The model was updated to the new format. I'm sure it's not quite right
but not a lot of work to update.
Yep, just needs to be verified. I haven't tried it in 1.1 since.
All fine except for the xerces generated parser.
-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
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
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 30, 2004 2:10 PM
To: Maven Developers List
Subject: Re: versioning of maven-model drops
[...]
This will still work - you should be able to drop in
maven-model-4.0.1
and it still works
Next question is what we can really do with converters between major
versions of POMs: e.g. between v3 and v4
and where and how such converter will be used?
I believe Trygvis has already implemented one for continuum. Correct, it
is only partially automated, but it can warn on ignored info,
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
Brett Porter wrote:
Next question is what we can really do with converters between major
versions of POMs: e.g. between v3 and v4
and where and how such converter will be used?
I believe Trygvis has already implemented one for continuum. Correct,
it is only partially automated, but it can
On Wed, 2004-12-01 at 00:27, Michal Maczka wrote:
Brett Porter wrote:
I am just trying to propose something simpler as I am afraid that there
will be way too many converters and parsers.
The whole point in trying to stabilize the v4 POM is so that there will
not be a proliferation of parsers
Quoting Michal Maczka [EMAIL PROTECTED]:
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
I don't know how this affects your question, but my immediate use case for
maven-model is to load up a POM for a project, and then attempt to load up
each dependencies POM. I'd like to be able to generate a report that lets
me know that I am using the latest and greatest versioned artifact of
Hi Jason,
I thought the best was that the current one was always o.a.m.model.*,
and all the historical ones were included with package name.
ie in maven-model-4.0.0, there is just o.a.m.model; in maven-model-4.0.1
there is o.a.m.model.* and o.a.m.model.v400.*.
An exception is for the v3.0.0
On Mon, 2004-11-29 at 14:32, Eric Pugh wrote:
I don't know how this affects your question, but my immediate use case for
maven-model is to load up a POM for a project, and then attempt to load up
each dependencies POM. I'd like to be able to generate a report that lets
me know that I am using
On Mon, 2004-11-29 at 14:49, Brett Porter wrote:
Hi Jason,
I thought the best was that the current one was always o.a.m.model.*,
and all the historical ones were included with package name.
ie in maven-model-4.0.0, there is just o.a.m.model; in maven-model-4.0.1
there is o.a.m.model.* and
14 matches
Mail list logo
