Automate modifying Maven site index when releasing

[Kalle Korhonen <ka...@gmail.com>]

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

Re: Automate modifying Maven site index when releasing

[Kalle Korhonen <ka...@gmail.com>]

This can be accomplished with a Doxia snippet macro (
http://maven.apache.org/guides/mini/guide-snippet-macro.html) and a little
bit of creative Ant scripting. Might be too custom of a use case to make it
a plugin.

Kalle


On Tue, Feb 3, 2009 at 11:00 PM, Kalle Korhonen
<ka...@gmail.com>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
>

Re: Automate modifying Maven site index when releasing

[Kalle Korhonen <ka...@gmail.com>]

On Wed, Feb 4, 2009 at 3:39 PM, Wendy Smoak <ws...@gmail.com> wrote:

> On Wed, Feb 4, 2009 at 4:34 PM, Kalle Korhonen
> <ka...@gmail.com> wrote:
>
> > The whole point of this thread was to automate it.
>
> How about...
>  - write a plugin to modify the text of the file.
>  - use the scm plugin to commit the change.
>
>
Yes, considered, as said I thought maybe it's too specific of a use case to
make it a plugin. But certainly, that'd work as well.

Kalle

Re: Automate modifying Maven site index when releasing

[Wendy Smoak <ws...@gmail.com>]

On Wed, Feb 4, 2009 at 4:34 PM, Kalle Korhonen
<ka...@gmail.com> wrote:

> The whole point of this thread was to automate it.

How about...
 - write a plugin to modify the text of the file.
 - use the scm plugin to commit the change.

-- 
Wendy

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: Automate modifying Maven site index when releasing

[Kalle Korhonen <ka...@gmail.com>]

On Wed, Feb 4, 2009 at 3:19 PM, Dennis Lundberg <de...@apache.org> wrote:

> Kalle Korhonen wrote:
> > On Wed, Feb 4, 2009 at 2:32 PM, Dennis Lundberg <de...@apache.org>
> 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: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>


 --
> Dennis Lundberg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

Re: Automate modifying Maven site index when releasing

[Dennis Lundberg <de...@apache.org>]

Kalle Korhonen wrote:
> On Wed, Feb 4, 2009 at 2:32 PM, Dennis Lundberg <de...@apache.org> 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.

> 
> 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: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
> 


-- 
Dennis Lundberg

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: Automate modifying Maven site index when releasing

[Kalle Korhonen <ka...@gmail.com>]

On Wed, Feb 4, 2009 at 2:32 PM, Dennis Lundberg <de...@apache.org> 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.

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: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

Re: Automate modifying Maven site index when releasing

[Dennis Lundberg <de...@apache.org>]

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.

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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org