incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Emmanuel Lécharny <>
Subject Re: [DISCUSS] Communicating intent around non-release, downstream integration binary artifacts
Date Wed, 24 Jun 2015 20:30:18 GMT
Le 24/06/15 22:14, David Nalley a écrit :
>>> Going back to the example of libraries published as Maven artifacts
>>> for those projects already publishing SNAPSHOTs these only get
>>> published to the Apache Nexus server ( and are
>>> not synced to Maven central.
>> So ? SNAPSHOTs are visible, anyone can download them, and they are not
>> endorsed by apache. They are just stored there because it's convenient,
>> not because it's official or whatever makes an ASF release.
> The reasoning is that artifacts on repository.a.o are hard to find,
> hard to come across. It's not in Maven Central.
> We aren't hiding them, but for someone to consume them would require
> them taking explicit action that short of them being in the project
> community they won't know about.
> We don't publish those artifacts to central, because people would
> easily find and consume them.

That does not make a policy. You are just making it a bit more
complicated for our user to fool themselves, which is always good. In
any case, everything is still plainly visible to anyone, hopefully.

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

View raw message