I just updated the download page to reference Maven Central in the meantime to ensure infra@ won't yell at us :) The number of end users downloading .jars directly instead of via Maven or Ant+Ivy I would assume is very low - shouldn't hurt anything while we figure out the final solution.
We can definitely host it ourselves if we want, and I can change the links again at that time. My main hope is that can be automated in as much as possible. Any recommendations? My suggestion last night that I couldn't formulate very well was basically this: 1. Unzip the 'official' source release. 2. Build the project in its entirety from the .zip 3. tarball up the built project (with target directories, etc) and upload it to dist 4. Untar it on dist 5. Change the links on the dowload page to reference the dist target locations. Its not as clean as only uploading the raw .jars and .asc/.sha1/.md5 files, but it is easily automated. If there is another mechanism that easily allows us to automate upload of only what would be downloaded, that'd be better. I'm in favor of whatever is easiest. Les On Thu, Jun 3, 2010 at 12:37 PM, Kalle Korhonen <kalle.o.korho...@gmail.com> wrote: > On Thu, Jun 3, 2010 at 12:25 PM, Les Hazlewood <lhazlew...@apache.org> wrote: >> I'm not sure that we would need that for the binary .jar downloads on >> the download page [1] (in the 'Binary Distribution' section, see the >> 'Artifact' table column). By linking directly to the Maven Central >> url, we guarantee that the ASF infrastructure won't be 'hit', since >> apparently that's what people are concerned about. >> It might make sense to use the .cgi for the source release .zip >> though, which Kalle is taking care of I believe. Kalle, do you need >> that? > > We could go either way on that but given that Maven users likely don't > use the source release and that it might be more proper to point to > the dist location for it, we might just as well be nice to Sonatype > (somebody always has to pick up the tab!). > > Kalle > > >> On Thu, Jun 3, 2010 at 12:10 PM, Craig L Russell >> <craig.russ...@oracle.com> wrote: >>> Hi Les, >>> >>> On Jun 3, 2010, at 10:51 AM, Les Hazlewood wrote: >>> >>>> Thanks for the clarification. And yes, I totally agree that the >>>> download page should be changed to point to central >>> >>> There's a .cgi script that points to mirrors that all projects copy. It's >>> not a big deal right now because of the small number of downloads we expect >>> for an incubating release, but it's good to get it right for practice. >>> >>> If you need help finding the mirror .cgi script let me know. >>> >>> Craig >>> >>>> instead of the ASF >>>> repo. I'll make that change now. >>>> >>>> Thanks, >>>> >>>> Les >>>> >>>> On Thu, Jun 3, 2010 at 7:26 AM, Kalle Korhonen >>>> <kalle.o.korho...@gmail.com> wrote: >>>>> >>>>> Yes, that's the entire source. I missed your note on the dist, will do. >>>>> >>>>> Kalle >>>>> >>>>> >>>>> On Thu, Jun 3, 2010 at 1:14 AM, Craig L Russell >>>>> <craig.russ...@oracle.com> wrote: >>>>>> >>>>>> Hi Kalle, >>>>>> >>>>>> When I looked at the release, it looked like the proper official source >>>>>> release is the shiro-root artifacts with their checksums and signatures. >>>>>> >>>>>> Specifically, the shiro-root-1.0.0-incubating-source-release.zip and >>>>>> checksums and signatures from >>>>>> >>>>>> https://repository.apache.org/content/repositories/staging/org/apache/shiro/shiro-root/1.0.0-incubating/ >>>>>> >>>>>> If I understand this, it's the entire source tree that constitutes a >>>>>> release. >>>>>> >>>>>> I think I commented earlier that these artifacts are those that would be >>>>>> put >>>>>> into the dist/incubator/shiro/1.0.0-incubating directory. >>>>>> >>>>>> Craig >>>>>> >>>>>> On Jun 2, 2010, at 11:16 PM, Kalle Korhonen wrote: >>>>>> >>>>>>> Whoops. One thing missing from the release - we don't have anything in >>>>>>> the Apache Shiro distribution area. My oversight, been living in Maven >>>>>>> land for too long. I checked and created the Shiro directory already, >>>>>>> the only real question is what should we put in there? Just the >>>>>>> shiro-all with keys (the primary artifact from >>>>>>> >>>>>>> >>>>>>> http://repo2.maven.org/maven2/org/apache/shiro/shiro-all/1.0.0-incubating/)? >>>>>>> According to the instructions, project documentation doesn't go in >>>>>>> there. Mentors have any advice? Maven or not, I think we should add >>>>>>> some of the release packages in the distribution area, especially >>>>>>> since it's tracked by Incubator clutch. >>>>>>> >>>>>>> Kalle >>>>>> >>>>>> 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! >>>>>> >>>>>> >>>>> >>> >>> 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! >>> >>> >> >
