| Property buckminster.build.timestamp no longer ISO-8601? [message #540851] |
Thu, 17 June 2010 09:27  |
Eclipse User |
|
|
|
Hi,
prior to r11456, the buckminster.build.timestamp was supposed to be in
ISO-8601 format (as documented). However, now the format needs to be one
of the common formats:
public static final String[] commonFormats = new String[] {
"yyyy-MM-dd_HH-mm-ss", "yyyyMMddHHmm", "yyyyMMdd-HHmm", "yyyyMMdd" };
//$NON-NLS-1$ //$NON-NLS-2$ //$NON-NLS-3$ //$NON-NLS-4$
Is this intentional, or accidental and will it at some point be reverted
to ISO-8601 (or will ISO-8601 be added to those "common formats")? Note
the difference is in one line -- the new code calls timestamp =
DateAndTimeUtils.fromString((String) isoTS); while the old code called
timestamp = DateAndTimeUtils.fromISOFormat((String) isoTS);
Thanks.
--Peter
|
|
|
| Re: Property buckminster.build.timestamp no longer ISO-8601? [message #540868 is a reply to message #540851] |
Thu, 17 June 2010 09:47  |
| Eclipse User |
|
|
|
Hi Peter,
That's a regression. The ISO-8601 format should still be one of the supported formats. Can you please enter a bugzilla
for this?
Thanks,
- thomas
On 06/17/2010 03:27 PM, Peter Nehrer wrote:
> Hi,
>
> prior to r11456, the buckminster.build.timestamp was supposed to be in
> ISO-8601 format (as documented). However, now the format needs to be one
> of the common formats:
>
> public static final String[] commonFormats = new String[] {
> "yyyy-MM-dd_HH-mm-ss", "yyyyMMddHHmm", "yyyyMMdd-HHmm", "yyyyMMdd" };
> //$NON-NLS-1$ //$NON-NLS-2$ //$NON-NLS-3$ //$NON-NLS-4$
>
> Is this intentional, or accidental and will it at some point be reverted
> to ISO-8601 (or will ISO-8601 be added to those "common formats")? Note
> the difference is in one line -- the new code calls timestamp =
> DateAndTimeUtils.fromString((String) isoTS); while the old code called
> timestamp = DateAndTimeUtils.fromISOFormat((String) isoTS);
>
> Thanks.
>
> --Peter
|
|
|
|
Powered by
FUDForum. Page generated in 0.02682 seconds
Home