On Feb 5, 2008 9:51 AM, Torsten Curdt <[EMAIL PROTECTED]> wrote:
>
> On 05.02.2008, at 02:34, Niall Pemberton wrote:
>
> > The ant plugin I've been playing with in the Sandbox provides a way to
> > generate custom JIRA issue tracking pages and download pages for
> > components:
> >
> > http://commons.apache.org/sandbox/commons-build-plugin/
> >
> > If we add it to the commons-parent, then each component just need a
> > few properties configuring to generate those pages. It uses templates
> > to generate the pages - making it easy to keep all components
> > consistent. Also currently the download pages are part of the main
> > commons site - rather than the individual component sites - moving it
> > to part of the components site IMO improves things since the user
> > remains within the component site rather than navigating away to
> > download. It can generate "proper" or "sandbox" flavour JIRA Issue
> > Tracking pages and either a "download page" or "no download availble
> > page" for sandbox/unreleased components. It also caters for component
> > sites being in either the default m1 or m2 locations.
> >
> > WDYT - good idea or waste of time?
>
> Do you have some examples online somewhere?

Example of changes required to commons-parent pom and  chain pom:
  http://people.apache.org/~niallp/chain/buildplugin-chain-example.patch

Example of the JIRA page generated:
  http://people.apache.org/~niallp/chain/issue-tracking.html

Example of the Download page generated:
  http://people.apache.org/~niallp/chain/download_chain.html

As you can see, they're pretty much what we have at the moment - but
all our JIRA Issue Tracking pages are "hand-crafted" - this provides
an easy way to generate and using a template - and the download pages
are not part of the components site - which this now is (obviously
would need the associated cgi in same dir to work)

Niall

> cheers
> --
> Torsten

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to