On Wed, Feb 4, 2009 at 3:19 PM, Dennis Lundberg <[email protected]> wrote:
> Kalle Korhonen wrote: > > On Wed, Feb 4, 2009 at 2:32 PM, Dennis Lundberg <[email protected]> > wrote: > > > >> You should be able to use the available ${project.*} properties in your > >> index.apt.vm file to add the *current* release. You would still need to > >> manually add the *previous* releases before you start the release > >> process though. > > > > > > Of course, that's given, but it doesn't get me very far. I need to add > the > > info about the current release to a file anyway so it shows as a > "previous > > release" the next time around. > Yes, but this way you don't have to do it in the *middle* of the > release. Instead you can add it as a manual pre- or post-release step. The whole point of this thread was to automate it. Kalle > > Kalle Korhonen wrote: >>> As part of our release process we create a distribution package that is >>> automatically published with site deploy to make it available for users >> to >>> download it (we also use changes plugin to send release announcement >>> automatically). One small, but annoying manual step we still haven't been >>> able to automate is to add a link to the new release on our site index >> page >>> (we use APT format with Velocity filtering - i.e. index.apt.vm for >> example). >>> The links to the previous releases are preserved on the page, so >> basically >>> the page would have to modified then checked back in while doing >>> release:prepare. Is anybody doing anything like this, any suggestions how >> to >>> make it all automatic? Alternative ways - like always generating the >> links >>> to releases from the the available tags might work as well (perhaps >> doable >>> but doesn't look very straightforwarded to me). >>> >>> Kalle >>> >> >> -- >> Dennis Lundberg >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > -- > Dennis Lundberg > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
