incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Davanum Srinivas" <>
Subject Re: Again: The Maven Repository
Date Thu, 26 Jun 2008 12:35:44 GMT

My guess is this issue will keep coming up *TILL* the folks who want
this to happen get their way! sigh! :(

-- dims

On 6/26/08, Jukka Zitting <> wrote:
> Hi,
> So far, despite lots of discussion, we haven't come up with a
> consensus on this issue. I plan to start a majority vote on this to
> settle the debate one way or another, but before that (and to avoid
> dissolving the vote thread into another debate) I'd like to ask anyone
> interested to bring up any new insight that hasn't yet been discussed.
> Much of the debate so far has been rather abstract, so I think it
> would help to highlight two concrete examples of what issues this
> policy causes:
> a) The incubating Apache Sling project just released a set of
> artifacts in the m2-incubating-repository. Since these artifacts are
> not in the standard repository, we end up with issues [1] and need to
> document workarounds [2]. Is this really necessary?
> b) The incubating Apache PDFBox project will sooner or later make an
> incubating release. Previous PDFBox releases are already in the
> central Maven repository and are being heavily used from there. Do we
> really need to require (and instruct) downstream users to modify their
> Maven settings just to get a PDFBox version upgrade?
> The current Maven repository policy makes life more difficult for many
> incubating projects and their users. Are these drawbacks worth the
> benefits?
> [1]
> [2]
> BR,
> Jukka Zitting
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

Davanum Srinivas ::

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message