Wayne Fay wrote:
>
> On 4/21/07, Jose Alberto Fernandez <[EMAIL PROTECTED]> wrote:
>> So if I say <quality>BETA</quality> then no alpha bundle (a bundle
>> containing alpha software) will be selected.
>
> Who exactly decides what the quality is for a given release? Outside
> of a handful (literally) of major apps/projects (Linux kernel and
> Apache webserver come to mind), very few seem to have a good sense for
> this, and I'm not even positive I'd totally trust myself with that
> decision for code I'm working on at times. We already have enough
> trouble getting projects to provide us with very basic poms, much less
> providing full poms with these kinds of details. So right off the bat,
> this sounds like a losing proposition for 95% of the projects in the
> wild.
>
> Also, what happens when I specify <quality>BETA</quality> and depend
> on artifact xyz which brings in xyz-1.0.2-BETA which has a dependency
> on artifact abc-2.0.1-ALPHA? Will you expect Maven to pick xyz-1.0.1
> (final) which depended on abc-2.0.0 (final) since it can't satisfy all
> transitive requirements with BETA quality code? This just doesn't seem
> manageable for anyone...
>
> Of course, its much easier to find problems than solutions, so I don't
> want to discourage you from continuing the discussion. I just don't
> think this is the solution.
>
> Wayne
>
Does this problem come from the fact that the labels alpha, beta and final
are too tightly linked to a given release? Actually these are labels and
should be independent of the build. When revision 234 of xyz-plugin is
released, we might label it alpha, but if no defects are found after a lot
of of testing the we could call that same build final. It's still a build
of revision 234, but now it's final.
If we had this kind of separation between builds and labels then it would be
easier to solve the "all the transitive dependencies of maven final should
be final" problem.
A complete change in the handling of builds and labels would be too big for
maven right now, so a simpler approach in needed. Perhaps a simple way
could be found to promote alpha and beta releases to final once enough
testing has been done.
Ultimately it's a problem of governance, and with such a widely dispersed
leadership over a great number of small projects it's difficult.
David
--
View this message in context:
http://www.nabble.com/Remove-auto-resolution-of-plugin-versions-from-Maven-2.1-tf3560617s177.html#a10144515
Sent from the Maven Developers mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
