[ 
http://issues.apache.org/jira/browse/VELOCITY-169?page=comments#action_12329788 
] 

Will Glass-Husain commented on VELOCITY-169:
--------------------------------------------

Found this old issue.  Thanks for suggesting it.   If you are still interested, 
I'd be willing to commit this if you could write a unit test and documentation.

If you want a simpler way to contribute, you might put this into the Velocity 
wiki at
http://wiki.apache.org/jakarta-velocity/ContributedCode

> Let's see if we can make Texen task to SKIP file generation if the results 
> are UP TO DATE - working solution proposed
> ---------------------------------------------------------------------------------------------------------------------
>
>          Key: VELOCITY-169
>          URL: http://issues.apache.org/jira/browse/VELOCITY-169
>      Project: Velocity
>         Type: Improvement
>   Components: Texen
>     Versions: 1.3.1
>  Environment: Operating System: All
> Platform: All
>     Reporter: tagunov
>     Assignee: Velocity-Dev List
>     Priority: Minor
>  Attachments: TexenCond.java
>
> 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!

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to