Re: Re: How to supress the *.java.optionCheck files?

The reason behind this to fit into the Ant taskdef paradigm:

1. HTMLs are translated into Java in batch
2. All generated Java files are compiled with one command

This is where the speed up with Ant and XMLC comes from. The 
optionCheck file is generated along with the generated Java files. In 
Ant, these generated files are deleted during the clean task.

If you're using command like tool with "-keep" option, the optionCheck 
should be removed along with the .java files. If the optionCheck isn't 
removed, this is a bug!

David


On Nov 19, 2003, at 2:49 PM, Jacob Kjome wrote:

> At 10:52 AM 11/19/2003 +0100, you wrote:
> > Hi Jake!
> >
> > > I think they are used by the XMLC task to, somehow, track whether 
> > the files
> > > need to be regenerated or not.  I can't quite remember.  What 
> > problem are
> > > you having with them, exactly?  I think David Li would know more 
> > about
> > > this, as I think he added it.  He had a good reason.
> >
> > No really a problem - but after running the xmlc ant task, the
> > *.java.optionCheck files laying around. Would be good to have them 
> > deleted
> > automatically.
>
> Depends if they are needed for future runs of the XMLC taskdef.  David 
> (Li), can you fill us in on this?
>
> Jake
> _______________________________________________
> XMLC mailing list
> XMLC@xxxxxxxxxxx
> http://www.enhydra.org/mailman/listinfo.cgi/xmlc