@@ -498,20 +498,28 @@ public class GitCommitIdMojo extends AbstractMojo {
498498 * represents dates or times exported by this plugin (e.g. {@code git.commit.time}, {@code
499499 * git.build.time}). It should be a valid {@link SimpleDateFormat} string.
500500 *
501- * <p>The current dateFormat is set to match maven's default {@code yyyy-MM-dd'T'HH:mm:ssZ}.
502- * Please note that in previous versions (2.2.0 - 2.2.2) the default dateFormat was set to: {@code
503- * dd.MM.yyyy '@' HH:mm:ss z}. However the {@code RFC 822 time zone} seems to give a more reliable
504- * option in parsing the date and it's being used in maven as default.
501+ * <p>The current dateFormat will be formatted as ISO 8601
502+ * {@code yyyy-MM-dd'T'HH:mm:ssXXX} and therefore can be used as input to maven's
503+ * <a href="https://maven.apache.org/guides/mini/guide-reproducible-builds.html">
504+ * reproducible build</a> feature.
505+ *
506+ * Please note that in previous versions
507+ * (2.2.2 - 7.0.1) the default format was set to {@code yyyy-MM-dd'T'HH:mm:ssZ}
508+ * which produces a {@code RFC 822 time zone}. While such format gives reliable
509+ * options in parsing the date, it does not comply with the requirements of
510+ * the reproducible build feature.
511+ * (2.2.0 - 2.2.2) the default dateFormat was set to: {@code
512+ * dd.MM.yyyy '@' HH:mm:ss z}.
505513 *
506514 * <p>Example:
507515 *
508516 * <pre>{@code
509- * <dateFormat>yyyy-MM-dd'T'HH:mm:ssZ </dateFormat>
517+ * <dateFormat>yyyy-MM-dd'T'HH:mm:ssXXX </dateFormat>
510518 * }</pre>
511519 *
512520 * @since 2.2.0
513521 */
514- @ Parameter (defaultValue = "yyyy-MM-dd'T'HH:mm:ssZ " )
522+ @ Parameter (defaultValue = "yyyy-MM-dd'T'HH:mm:ssXXX " )
515523 String dateFormat ;
516524
517525 /**
0 commit comments