So,
The official and primary distribution of Shiro are the source bundles
found at dist/shiro/...
Anything else is a secondary distribution, including "binary" releases
also found at dist/shiro and m2 poms and jars.
Artifacts that are published at dist/shiro should be referenced via
the "download from mirror" technique. Artifacts that are published in
the m2 rsync repository can be downloaded simply by referencing them
in a maven pom. There's no need to have another way to download the
poms and jars.
Craig
On Aug 17, 2010, at 12:10 PM, Les Hazlewood wrote:
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
cached).
We unfortunately can't use m2 central as our primary distribution
source since that is not considered ASF infrastructure. At least
according to the publishing page:
"The Apache infrastructure must be the primary source for all
artifacts officially released by the ASF."
I think it's ok at the moment to have the links for the binary .jars
point to m2 central because they're not really official ASF releases -
we do it as a convenience. Although it would be a little nicer to
have all of our artifacts hosted by the ASF: someone has to pay the
download bandwidth costs, and it'd be better if the ASF (or one of
it's agreed mirror partners) did that instead of us passing the bill
transparently to Sonatype. Just a thought...
Cheers,
Les
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:craig.russ...@oracle.com
P.S. A good JDO? O, Gasp!
