Rahul Akolkar wrote:
On Fri, Jun 19, 2009 at 12:19 PM, Phil Steitz wrote:
sebb wrote:
On 19/06/2009, Phil Steitz wrote:
The commons-build plugin generates a component-specific download page
/ cgi that ends up in the component's web. We still have links on the
main download
On Fri, Jun 19, 2009 at 12:19 PM, Phil Steitz wrote:
> sebb wrote:
>>
>> On 19/06/2009, Phil Steitz wrote:
>>
>>>
>>> The commons-build plugin generates a component-specific download page
>>> / cgi that ends up in the component's web. We still have links on the
>>> main download page to a commo
sebb wrote:
On 19/06/2009, Phil Steitz wrote:
The commons-build plugin generates a component-specific download page
/ cgi that ends up in the component's web. We still have links on the
main download page to a common location for all of these. How are do
we keep these up to date? Do we
On 19/06/2009, Phil Steitz wrote:
> The commons-build plugin generates a component-specific download page
> / cgi that ends up in the component's web. We still have links on the
> main download page to a common location for all of these. How are do
> we keep these up to date? Do we need to m
The commons-build plugin generates a component-specific download page
/ cgi that ends up in the component's web. We still have links on the
main download page to a common location for all of these. How are do
we keep these up to date? Do we need to maintain two copies of the
download page and re
