You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@velocity.apache.org by bu...@apache.org on 2003/04/23 13:50:10 UTC

DO NOT REPLY [Bug 19246] New: - Let's see if we can make Texen task to SKIP file generation if the results are UP TO DATE - working solution proposed

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19246>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19246

Let's see if we can make Texen task to SKIP file generation if the results are UP TO DATE - working solution proposed

           Summary: Let's see if we can make Texen task to SKIP file
                    generation if the results are UP TO DATE - working
                    solution proposed
           Product: Velocity
           Version: 1.3.1
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: Texen
        AssignedTo: velocity-dev@jakarta.apache.org
        ReportedBy: tagunov@motor.ru


Hello, developers!

I know that in the general case we can not detect that the output of TEXEN 
ant task is newer then ALL the sources - cause we don't know all the sources.

But in a specific 
situation - if we assume that ALL THE SOURCE FILES are located in the TEMPLATEPATH directory and ALL 
THE FILES in the TEMPLATEPATH directory are template sources WE CAN compare their timestamp to 
the output file lastModified() timestamp.

I'm attaching a SAMPLE IMPLEMENTATION (the Ant 
task I'm using now) as an example -- it maybe a new Ant task (I called it TEXENCOND - conditional TEXEN) 
or a boolean flag on the regular TEXEN task.

Motivation: I use VELOCITY VERY EARLY in my build 
chain:
  TexenTask->JavaCC->JavaC
so not changing lastModified() on the files generated by 
Texen really saves an amount of build time and avoids lots of messages from JavaCC cluttering the 
screen.

And I can imagine even using it like this:
  TexenTask->JJTree->JavaCC-
>JavaC

Hoping the code I use for myself will be usefull for others too!

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