regarding the property name, I had an idea:
why not do like we already did for ${project.build.sourceEncoding}, ie. mimic
a future element in pom.xml, in build?
could be project.build.timestamp?
Le samedi 28 septembre 2019, 17:55:24 CEST Hervé BOUTEMY a écrit :
> Achieving Reproducible Builds require only one parameter: plugins that
> create zip or tar archives require a fixed timestamp for entries
>
> Putting that parameter as a pom property with a well known name and value
> format permits to share the configuration between every packaging plugin.
> This also has the advantage that child poms will inherit from parent value,
> and eventually override.
>
> The question is: *what property name and what value format should we keep?*
>
> For the PoC, I chose to extrapolate from a convention from Reproducible
> Builds project, which is very Linux-oriented: SOURCE_DATE_EPOCH environment
> variable, that I transformed into source-date-epoch property name, keeping
> the "date + %s" value
> https://reproducible-builds.org/docs/source-date-epoch/
>
>
> But I feel we can do a more user-readable solution by choosing another name
> and format, like "reproducible-build-timestamp" with an ISO-8601 combined
> date and time representation
>
>
> WDYT? Any other idea?
>
> Regards,
>
> Hervé
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
