Re: CVS [was: Re: Ozone Doc Project]

[Eric Richardson <eric@milagrosoft.com>]

Lars Martin wrote:
> 
> Hi Eric.
> 
> On Tue, 29 May 2001 11:08:56 -0700
> Eric Richardson <eric@milagrosoft.com> wrote:
> 
> > Great. I downloaded from CVS and made sure I had java in my PATH and
> > JAVA_HOME set and it worked.
> 
> Great. Any experiences with Windows?
> 
> > The one thing that worries me is the lib directory. FOP and Xalan(XSLT)
> > are two independent products that both rely on xerces.jar. I guess it
> > could be coincidence that the two are compatable right now. I suggest a
> > lib/fop and a lib/xslt so we can independently upgrade xslt which could
> > be xalan or xt or saxon and fop which I think there is only one open
> > source java version.
> 
> Yes, you're right here. My intention for only *one* lib directory was
> my hope to keep the distribution as small as possible. Therefore I
> checked the compatibility of both packages (HTML & PDF). If it is
> necessary to split the library directory in the future because of
> incompatibility then we can do this. Right now I don't see the necessary
> to do this. But you've commit access - if the current structure doesn't
> match your needs then simply modify it. My work was just the starting
> shot for the ODP.
Okay - we'll see how it goes.

Maybe we can zip the stylesheets and then have a simple install that
unzips as this would be better for CVS rather than all the individual
files. The install could call jar or we could have a task that does it
first time somebody trys to build. What do you think?

The driver files are there to modify and override templates in the
stylesheet distribution if needed.
> 
> > I'll work on the documentation guide for this project first.
> 
> Cool. We look forward to working with you on this project. :-)
> 
> > I was also wondering if ant has rules or someway to do something like
> > you can do in make.
> >
> > make foo.c
> >
> > This uses the .c to .o rule. I'd like to do the following.
> >
> > ant doc-dev-guide.xml
> >
> > The reason I'd like to do this is so we don't have to add two rules for
> > each doc, one for html and one for pdf. My box is rather slow so I'd
> > prefer to only transform the doc I'm working on since as well.
> 
> No, I don't think this is possible with Ant.
I may try the call function so we can make really short rules for each
doc and then one rule to do the work. I tried the style task yesterday
but it didn't work. I was using the 1.3 binary version - Is that the
version we are using in docs and ozone proper?

Let you know if I can get it to work.

eric :-)