> Downloaded the src.gz and checked the md5, result OK. (Don't know how to > check the ASC or SHA, but I can do if someone gives me some guidence, is > there a tutorial I can follow?)
If you're on Linux, you can run: $ gpg --verify foo-1.0.tar.gz.asc foo-1.0.tar.gz $ sha1sum foo-1.0.tar.gz I don't know what the procedure is on the Mac or Linux. > Followed instructions in BUILD, which appears to work OK except that the md5 > for the generated src.gz is different from the one I downloaded. That's because each JAR is timestamped, which yields a *slightly* different JAR, and hence a different checksum. > I also notice the if you run the install target and then re-run the dist > target, you get a different md5 for the src.gz every time you do 'ant > install' followed by 'ant dist'. I don't know if this is a problem but it > looks as though the dist target picks up stuff left over from the install > target, or else something is changing. Yeah, again, it's the timestamps in the JAR files that are changing. > I would have thought the first thing > dist should do is 'clean' everything down to a known state? install cleans first since it produces the binaries. dist doesn't need to, since it just bundles up the source. > Also, is there a quick way to run the demos after a binary build? I know > they are on the web, but it would be a good sanity check for users to prove > that what they just downloaded / checked out works OK as well as compiles. > I couldn't find any HTML wrappers for the demos and I also noted that > non-java resources in the source folder weren't copied in to the ant-bin > folder. I think it would be good to have a HTML wrapper for each demo. Yeah this could be useful. Currently, the deploy target (undocumented) puts all JAR files in a deploy directory and a few demo html files, but maybe we should promote this to a documented target and create html pages for all demos.
