Let's be clear, the central repo can host apache incubating artifacts,
it's not its business, it's an ASF business.
Now, only the ASF can publish under org.apache groupId through the
repos setup in the ASF boxes that are automatically setup
But if John Doe decides to publish an incubator artifact under
com.johndoe there's nothing the ASF can do as the ASL grants
redistribution. Now it's up to the users to trust com.johndoe
artifacts.
On 3/15/07, Jochen Wiedmann <[EMAIL PROTECTED]> wrote:
I can understand that the Apache "dist" directory is something
reserved for certain artifacts. Fact is, the ibiblio repository (as
opposed to the incubator repository) is not.
The ibiblio repository is specifically designed to hold artifacts of
all kinds, if the license permits. There are all kind of jar files of
all kind of sources. If artifacts are in the designated incubator
repository, then nothing prevents external users from uploading them
to Ibiblio, which is usually done sooner or later. (If the artifacts
are actually in use.)
In other words, your intention that users have "to configure any
repository" is lost. You cannot prevent that. Or are you telling me
that the owner of the incubator artifacts (typically the ASF) reserves
particular distribution rights, which are limiting the ASL? All you
achieve is that the POM ifiles of ncubator artifacts typically have a
lesser quality, because they aren't maintained by the project owners.
Jochen
--
Emacs 22 will support MacOS and CygWin. It is not yet decided, whether
these will be used to run Emacs or the other way round.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
