maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Bourg (JIRA)" <>
Subject [jira] [Commented] (MJAVADOC-619) Maven Javadoc bottom claims copyright for future years
Date Mon, 05 Aug 2019 21:03:00 GMT


Emmanuel Bourg commented on MJAVADOC-619:

The patch I implemented in Debian is about supporting [SOURCE_DATE_EPOCH |]
in the Javadoc plugin. The adoption of SOURCE_DATE_EPOCH is slowly growing across a wide variety
of tools, but as I understand there is still some resistance to support it in the Maven ecosystem
(mostly because the environment variable approach looks a bit hackish, but that's really the
lowest and only common denominator of very different tool ecosystems).

Maybe a less controversial change would be to use the build date in the javadoc plugin (from
{{MavenSession.getStartTime()}}) instead of the current date. So if at some point there is
an agreed upon mechanism to override the build date centrally (either by supporting SOURCE_DATE_EPOCH,
using the date of pom.xml, or a mix of both) then the javadoc plugin will benefit from it.
And this would allow Debian to drop its patch since the build date is already [overridden|].
There would be just one issue left to override the timezone to property format the date.

> Maven Javadoc bottom claims copyright for future years
> ------------------------------------------------------
>                 Key: MJAVADOC-619
>                 URL:
>             Project: Maven Javadoc Plugin
>          Issue Type: Bug
>    Affects Versions: 3.1.1
>            Reporter: Bernhard M. Wiedemann
>            Priority: Major
> Originally filed at
> []
> includes {{{currentYear}}}
> []
explains why this is bad (not only for reproducible builds)
> Debian worked already around this with
> []
> but I think, this warrants a more general patch.

This message was sent by Atlassian JIRA

View raw message