Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <dev@commons.apache.org>
Received-SPF: pass (athena.apache.org: domain of niall.pemberton@gmail.com
 designates 64.233.184.229 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=FytY31hBBNh0ggutBKPPlpC3VEX24uoqua1ikGVESOD65qlgxiG2gygkfA0dQ5pzVTSgfUeQqQABe/shKnD/Szx2OPO7pxPC39W3rdfx/19ToGHgsM3EuikPwDiY3eikyR7ucKjhNlw3x9LSIaSvpGxNmzw5GiEckSM/GVpoDpM=
Message-ID: <55afdc850802051240i47829aedre0578c0f61329a1d@mail.gmail.com>
Date: Tue, 5 Feb 2008 20:40:01 +0000
From: "Niall Pemberton" <niall.pemberton@gmail.com>
To: "Jakarta Commons Developers List" <dev@commons.apache.org>
Subject: Re: [all] Commons Build Plugin
In-Reply-To: <4107BC89-1C1F-4939-9603-B29652EC2AB5@apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <55afdc850802041734r5f51d45fjb42356483f629900@mail.gmail.com>
	 <4107BC89-1C1F-4939-9603-B29652EC2AB5@apache.org>

On Feb 5, 2008 9:51 AM, Torsten Curdt <tcurdt@apache.org> 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: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org