Hi Wendy! Attaching the assemblies as well will not give the maven users an additional benefit. This would only duplicate the space used on the repo. After we release with maven, the repo already includes the sources and SVN got tagges. So anyone working with maven can check it our from there.
The tar.gz distro ist targeted for people without maven and also for archiving reasons - but as mentioned: imho it doesn't make sense to pollute the main repo with those 2x6MB (remember: dist-all and dist-binary also include ALL the dependencies needed!) Configuring <createChecksums> in the maven-install-plugin did the trick for me. But thanks for mentioning the PGP plugin. I will definitely give it a try! LieGrue, strub --- Wendy Smoak <[email protected]> schrieb am So, 11.1.2009: > Von: Wendy Smoak <[email protected]> > Betreff: Re: md5 for assemblies - how do you do it? > An: "Maven Users List" <[email protected]> > Datum: Sonntag, 11. Januar 2009, 16:29 > On Sun, Jan 11, 2009 at 4:30 AM, Mark Struberg > <[email protected]> wrote: > > > First, we'll do the openwebbeans build with the > maven-release-plugin. So SVN gets tagged, all modules are > deployed to the maven-repo, etc. > > Later we will additionally start building the > distribution packages manually from this tag. The created > zips and tar.gzs will be hosted on the incubator page for > all people/projects who are interested and do _not_ use > maven. > > If you go ahead and attach the assemblies, you can do this > all at > once, and get the checksums. You didn't mention PGP > signatures, but > that will happen too, assuming you have the plugin > configured. > > You can then move (or just copy) the > zip/tar.gz/checksum/pgp > signatures out of the staging repo (renaming them as > necessary), and > you'll have the files you need for the /dist area. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
