on: Raju Bitter [mailto:r.bitter.mailingli...@googlemail.com]
Gesendet: Mittwoch, 12. September 2012 16:21
An: flex-dev@incubator.apache.org; jef...@dot-com-it.com
Betreff: Re: Javadoc for Falcon
>> I'd check a zipped version of the docs into Subversion.
> I'm pretty sure that it is an &quo
>> I'd check a zipped version of the docs into Subversion.
> I'm pretty sure that it is an "Apache Way" no no to put binary files into
> the repository if it can be avoided. In this case, I don't believe zipping
> up generated docs is an unavoidable approach.
I think the decision should be based
On 9/11/2012 7:24 PM, Raju Bitter wrote:
I'd check a zipped version of the docs into Subversion.
I'm pretty sure that it is an "Apache Way" no no to put binary files
into the repository if it can be avoided. In this case, I don't believe
zipping up generated docs is an unavoidable approach.
On 9/11/2012 7:13 PM, Gordon Smith wrote:
How shall we make Falcon's Javadoc available?
1. Require developers to build it locally with 'ant javadoc'.
2. Have a build machine which builds it and posts it somewhere.
3. Check it into the Subversion repository somewhere.
- Gordon
I vote 1 and 2
On 9/11/12 7 :13PM, "Gordon Smith" wrote:
>How shall we make Falcon's Javadoc available?
>
>1. Require developers to build it locally with 'ant javadoc'.
I believe this choice would be the Apache way.
Carol
>2. Have a build machine which builds it and posts it somewhere.
>3. Check it into th
I'd check a zipped version of the docs into Subversion. Easy to
download, and you don't have a large number of generated files in the
repository. Most people interested in the docs will probably want the
code anyway, I'm not sure the docs need to be posted to a public URL.
- Raju
How shall we make Falcon's Javadoc available?
1. Require developers to build it locally with 'ant javadoc'.
2. Have a build machine which builds it and posts it somewhere.
3. Check it into the Subversion repository somewhere.
- Gordon
