Jason van Zyl wrote:
> [snip]
> > I'm not totally sold on this because I feel we should have *something*
> > in a checkout of the base module. I realize that the TDK will take care
> > of many things but some users/developers will want some docs.
> >
> > An idea which might work would be to add an Ant target for the docs so a
> > developer could run './build-turbine.sh docs' and the relevant module
> > would be checked out of CVS and any files that need to be built would be
> > generated. An echo message could alert the developer that a sizable
> > download was going to be taking place just to make sure there aren't
> > complaints about that.
>
> Sure, or we could just put a copy of resultant html in the docs
> directory, and update it with a cron job. The resultant html
> doesn't take up much room. That would be fine with me.
>
> So how about that, we'll make a separate documentation
> project, and put a copy of the resultant html in the
> turbine/docs directory.
Rather than a cron job, how about a script or Ant task kicked off
whenever there is a commit to the turbine-docs repository (via
loginfo/logaccum/whatever it's called). This script will generate new
documentation from what has just been checked into the repository, and
commit the output to the main turbine repository. This will provide us
with always up to date documentation, and since we don't have that many
documentation commits, this shouldn't take up too many cycles.
Daniel Rall
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
