On Tue, Feb 26, 2008 at 12:35 PM, James Carman <[EMAIL PROTECTED]> wrote: > On 2/26/08, Niall Pemberton <[EMAIL PROTECTED]> wrote: > > OK but I still don't see much benefit - if I'm creating a release > > candidate I have to zip up the artifacts and upload them to > > p.a.o/~niallp so no big deal to include the site as well. My > > preference is to keep it simple and I can't see me using this. I guess > > its not a big deal to include it, but does anyone else think its a > > good idea? > > You're right. It's really not that big of a benefit. But, it does > save at least one step (in a somewhat daunting process for the newbies > like me). I wish we could just issue one command and have the site > deployed where it's supposed to go and the distribution files built, > signed, checksummed (is that a word?), and copied to where they're > supposed to go. Now that would be automation! :)
OK so lets leave this for the moment and get version 8 of commons-parent out. We definetly need to improve this with at a minimum good docs - perhaps would be good to discuss at ApacheCon, hopefully with some maven gurus around. Niall --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
