commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From robert burrell donkin <robertburrelldon...@blueyonder.co.uk>
Subject Re: [general] Maven 'LATEST-RELEASE' tag suggestion
Date Sat, 07 Feb 2004 22:21:32 GMT

On 7 Feb 2004, at 21:32, Mark R. Diggory wrote:

> robert burrell donkin wrote:
>
>> On 7 Feb 2004, at 20:53, Mark R. Diggory wrote:
>> <snip>
>>> It also gives developers some room to work. If there is a global 
>>> nightly/weekly process for generating the commons site and its 
>>> sub-projects then in reality they probibly don't want the site 
>>> xref/xdocs generated off of thier bleeding edge all the time.
>> hmmm...
>> i'd probably want the best of both worlds - the latest and greatest 
>> version but also versions of the site for each release. i suppose 
>> that it'd be possible to do something with directories so 
>> commons/kool/current would contain the latest version but 
>> commons/kool/7.12.89/ would contain the documentation which was 
>> current when 7.12.89 was released.
>> just a suggestion (rather than a criticism)...
>> - robert
>
> No, thats a really good point about versioned javadoc. Javadoc for 
> version 1.0, 2.0, ..., Current of a subproject.
>
> This would require maintaining the content of previous release site 
> generations, pushing into a special directory reserved for its 
> archiving.

craig advocated something similar in the original commons release 
documents (but only kept the last release). it shouldn't be too great a 
burden to copy the current website into a specially numbered directory 
when a release is cut.

- robert


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message