This has not bean dealt with that way for many projects historically.
E.g. not all maven plugins are served via dist, but via repository.a.o.

LieGrue,
strub


> Am 20.04.2017 um 18:11 schrieb sebb <seb...@gmail.com>:
> 
> On 20 April 2017 at 11:08, Mark Struberg <strub...@yahoo.de.invalid> wrote:
>> The geronimo-spec jars do most probably not.
>> Should we set this up that way? Probably a good idea...
> 
> AIUI all source releases MUST be made through the ASF mirror system.
> 
> http://www.apache.org/legal/release-policy.html#source-packages
> http://www.apache.org/legal/release-policy.html#release-distribution
> 
> The source can also be made available through other channels, but the
> primary publication mechanism is via the ASF mirror system.
> 
>> LieGrue,
>> strub
>> 
>>> Am 20.04.2017 um 12:02 schrieb John D. Ament <johndam...@apache.org>:
>>> 
>>> Romain,
>>> 
>>> Releases are sourced based on commits to your dist directory.  Do xbean
>>> releases go through our normal mirroring (e.g. source releases)?
>>> 
>>> John
>>> 
>>> On Thu, Apr 20, 2017 at 5:56 AM Romain Manni-Bucau <rmannibu...@gmail.com>
>>> wrote:
>>> 
>>>> Hi guys,
>>>> 
>>>> working on geronimo board i realized https://reporter.apache.org/ can
>>>> provide misleading result. I suspect it comes from the fact geronimo uses
>>>> multiple jira projects.
>>>> 
>>>> Question is: how can we validate there is an issue (bug, config issue or
>>>> something else) regarding jira integration? for instance ATM it reports
>>>> last release in 2014 but we got several since (multiple xbean in 2015 for
>>>> instance).
>>>> 
>>>> Romain Manni-Bucau
>>>> @rmannibucau <https://twitter.com/rmannibucau> |  Blog
>>>> <https://blog-rmannibucau.rhcloud.com> | Old Blog
>>>> <http://rmannibucau.wordpress.com> | Github <
>>>> https://github.com/rmannibucau> |
>>>> LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
>>>> <https://javaeefactory-rmannibucau.rhcloud.com>
>>>> 
>> 
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
>> For additional commands, e-mail: dev-h...@community.apache.org
>> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Reply via email to