jira-importer commented on issue #176: URL: https://github.com/apache/maven-jar-plugin/issues/176#issuecomment-2956675889
**[S L](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=thesnoozer)** commented Hello, thanks for the quick feedback! Ok, fine with me if you want to be explicit and want to avoid certain edge cases. However IMHO the 2024-02-15T13:54:59+0100 is following ISO 8601 standard. Refer for example to the java doc https://docs.oracle.com/javase/8/docs/api/java/text/SimpleDateFormat.html#iso8601timezone https://docs.oracle.com/en/java/javase/21/docs/api/java.base/java/text/SimpleDateFormat.html#iso8601timezone Both docs mention the support for the following three cases: ```java OneLetterISO8601TimeZone: Sign TwoDigitHours Z TwoLetterISO8601TimeZone: Sign TwoDigitHours Minutes Z ThreeLetterISO8601TimeZone: Sign TwoDigitHours : Minutes Z ``` The 2024-02-15T13:54:59+0100 follows the TwoLetterISO8601TimeZone. Only the ThreeLetterISO8601TimeZone can be currently processed. Similar to what wikipedia claims https://en.wikipedia.org/wiki/ISO_8601#Time_zone_designators: ```java <time>Z <time>±hh:mm <time>±hhmm <time>±hh ``` The 2024-02-15T13:54:59+0100 follows \<time>±hhmm and therefore should be supported. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
