Sounds good to me. As a side note though, one of the things that is nice about a binary, non-source package is that I can download everything local to disk without needing to be connected to the internet to view documentation and reference .jars as a I need them.
I think it would be nice to create such a package for our next release. This is the reason for example, why Spring has a spring-3.0.2-with-dependencies.zip and a spring-3.0.2-with-docs.zip. When I wasn't a Maven or Ant+Ivy user, I really liked being able to have this 'one stop shop' download. How do other projects do this? I'm sure most of them don't have a 'use Maven or you'll have to everything on the internet' approach, right? Les On Thu, Jun 3, 2010 at 2:26 PM, Alan D. Cabrera <[email protected]> wrote: > > On Jun 3, 2010, at 2:24 PM, Kalle Korhonen wrote: > >> On Thu, Jun 3, 2010 at 2:03 PM, Les Hazlewood <[email protected]> >> wrote: >>> >>> 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. >> >> Lots of unzipping, tarring and untarring there. I was merely going to >> put the zip and the keys and possibly the shiro-all there and be done >> with it. > > I'm thinking that since this is what was voted on and checked, this is what > we should run with. > > > Regards, > Alan > >
