ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 45089] New: tstamp granularity attribute
Date Wed, 28 May 2008 14:11:36 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=45089

           Summary: tstamp granularity attribute
           Product: Ant
           Version: 1.7Alpha (nightly)
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: Core tasks
        AssignedTo: notifications@ant.apache.org
        ReportedBy: mfrasca@zonnet.nl


Created an attachment (id=22025)
 --> (https://issues.apache.org/bugzilla/attachment.cgi?id=22025)
simple implementation of enhancement.

here at office we need running a scheduled job every so many minutes.  we are
using windows and its task scheduler.  we are not guaranteed that the job will
be run within a minute from the scheduled time, but we need to timestamp our
files according to the desired time, not the actual time.

for this reason I thought I could use a "granularity" property in the tstamp
core task.  for our purposes it would be enough to assume "minutes" as unit...

this is an example of what I mean:
<tstamp granularity="15" >
  <format property="start.date" pattern="yyyy-MM-dd" timezone="Z"/>
  <format property="start.time" pattern="HH:mm:ss" timezone="Z"/>
</tstamp>

even if Windows was so busy that it could not serve the request before - say -
15:31:26, my start.time property would still be "15:30:00".  in fact this value
would be stored to the property until 15:44:59 (given 15 minutes
granularity)...

the implementation is very easy and we already have it here...  maybe it could
be useful to others, too...


-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

Mime
View raw message