You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Niall Pemberton <ni...@gmail.com> on 2008/02/05 02:34:36 UTC
[all] Commons Build Plugin
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?
Niall
P.S. I just upgraded from maven 2.0.7 to 2.0.8 and it doesn't work (on
windoze) so I had to revert to 2.0.7 :( - but hey AIUI working
properly is not a requirement for maven - just a nice-to-have!!!
http://maven.markmail.org/message/hmwabpxrq76mbp3l
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [all] Commons Build Plugin
Posted by Torsten Curdt <tc...@apache.org>.
Looks cool IMO +1
cheers
--
Torsten
On 05.02.2008, at 22:14, Niall Pemberton wrote:
> On Feb 5, 2008 8:40 PM, Niall Pemberton <ni...@gmail.com>
> wrote:
>> On Feb 5, 2008 9:51 AM, Torsten Curdt <tc...@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
>
> Also Sandbox (CSV) Example:
> http://people.apache.org/~niallp/csv/buildplugin-csv-example.patch
> http://people.apache.org/~niallp/csv/download_csv.html
> http://people.apache.org/~niallp/csv/issue-tracking.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
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [all] Commons Build Plugin
Posted by Niall Pemberton <ni...@gmail.com>.
On Feb 5, 2008 8:40 PM, Niall Pemberton <ni...@gmail.com> wrote:
> On Feb 5, 2008 9:51 AM, Torsten Curdt <tc...@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
Also Sandbox (CSV) Example:
http://people.apache.org/~niallp/csv/buildplugin-csv-example.patch
http://people.apache.org/~niallp/csv/download_csv.html
http://people.apache.org/~niallp/csv/issue-tracking.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
Re: [all] Commons Build Plugin
Posted by Niall Pemberton <ni...@gmail.com>.
On Feb 5, 2008 9:51 AM, Torsten Curdt <tc...@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
Re: [all] Commons Build Plugin
Posted by Torsten Curdt <tc...@apache.org>.
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?
cheers
--
Torsten
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org