shiro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kalle Korhonen <>
Subject Re: Shiro artifact distribution
Date Tue, 17 Aug 2010 18:52:52 GMT
On Tue, Aug 17, 2010 at 11:29 AM, Les Hazlewood <> wrote:
> Yes, it did slip - and don't worry, I didn't do anything :)
> I'll have to go back through the release threads - is there something
> that you used that automates copying the resources to that location?

No, I just manually copied them over.

> Also, just out of curiosity, why do we publish there instead of the
> mentioned location in the release-publishing.html page?

Hmm... that's the exact dist location. As of now, we are a sub-project
of the incubator so we publish under Incubator's dist location like
all of the other Incubator projects, and as a Maven-based project we
also publish to as well (which is synched to

> In any event, I'll change the wiki links to point to these artifacts
> instead of the m2 repo.

>From my reading of the release documentation either is fine. As a TLP
I don't think we have a strict requirement to publish to /dist, it's
just an option. However, Clutch checks for the existence of release
artifacts at /dist so we better keep the duplicates there. Going
forward, I don't think we need to worry about cgi scripts for using
mirros either, central is already load-balanced (and proxied and


> On Tue, Aug 17, 2010 at 10:49 AM, Kalle Korhonen
> <> wrote:
>> Hold your horses - I did that as well when I made the release. The
>> official incubator distribution area for our project is at
>>, see the files there. I'm
>> sure I mentioned this at the release time but perhaps slipped through
>> your eyes.
>> Kalle
>> On Tue, Aug 17, 2010 at 10:35 AM, Les Hazlewood <> wrote:
>>> Per the Incubator list, we need to ensure our source distribution
>>> comes from Apache's mirrored infrastructure.  Kalle, I noticed that
>>> you changed the links in the meantime to point to the m2 repo
>>> (thanks), but we're mandated to distribute from the ASF
>>> infrastructure.  The links to the .jars point to m2 as a convenience,
>>> but since they're not a source distro, the ASF doesn't care about them
>>> as much - we just can't do that with our source distro.
>>> I was just going to place them in a directory under the 'static'
>>> directory of our website on  At least this is what
>>> is recommended by [1].  Any objections?
>>> Les
>>> [1]

View raw message