Issue #1842: Fix issue where start time of in progress VTEC events was being set

to 991130T0000Z.


Former-commit-id: 5bfa13b5bf [formerly cf21fb8fb3] [formerly 2281f4abc5 [formerly e6ad90e07a4af553edcb79ce71790f339b3f4ed5]]
Former-commit-id: 2281f4abc5
Former-commit-id: ea42ffa3e5
This commit is contained in:
David Gillingham 2013-07-19 11:19:52 -05:00 committed by Richard Peter
parent 682bf1ea10
commit c14ab8225f

View file

@ -41,6 +41,9 @@ import com.raytheon.viz.texteditor.util.VtecUtil;
* Date Ticket# Engineer Description
* ------------ ---------- ----------- --------------------------
* May 14, 2013 #1842 dgilling Initial creation
* Jul 19, 2013 #1842 dgilling Use VtecUtil.replaceFirstVtecString()
* to ensure start times of in progress
* events aren't set to the wrong time.
*
* </pre>
*
@ -94,7 +97,11 @@ public class GFEVtecUtil {
vtec.getPhensig(), true);
vtec.setSequence(newEtn);
}
vtecMatcher.appendReplacement(finalOutput, vtec.getVtecString());
vtecMatcher
.appendReplacement(
finalOutput,
VtecUtil.replaceFirstVtecString(
vtec.getVtecString(), vtec));
}
vtecMatcher.appendTail(finalOutput);
return finalOutput.toString();