Sorry, that didn't sound too clear - I was thinking that we keep the download page as it is, but link to each .jar/sha1/md5 to a directory that is the built project (i.e. /www/incubator.apache.org/shiro/static/releases/1.0.0-incubating = exploded directory of the built 1.0.0-incubating release .zip). Then we can just set up a symlink to point to the latest release as each one comes out. Does that make more sense?
Les On Wed, Jun 2, 2010 at 11:42 PM, Les Hazlewood <lhazlew...@apache.org> wrote: > I would assume just a built version of the project in its raw form > would be ok. Then we could link to the respective target/* > directories to the actual .jar files. I don't know if the target > directories contain the hashes, but I would assume so... > > On Wed, Jun 2, 2010 at 11:16 PM, Kalle Korhonen > <kalle.o.korho...@gmail.com> 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 >> >
