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

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Environment: Operating System: All; Platform: All
• Bugzilla Id: 19246
• Assignee: Unassigned
• Reporter: tagunov
• Created: 23/Apr/03 18:50
• Updated: 09/Apr/07 12:16

Description

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!