very good question: this was a key question to me, that lead me to the PoC to 
test and see
this PoC showed a basic fact: a POM will inherit the value from his parent

Then once a parent POM has a "reproducibility" timestamp, child POMs inherit 
reproducible configuration, and can eventually override value

I imagine that we'll do a maven-release-plugin feature to update the value to 
match release timestamp
But we can start by updating the value by hand if we want to have a value that 
has a better meaning that the inherited one

Regards,

Hervé

Le samedi 28 septembre 2019, 22:52:04 CEST Enrico Olivelli a écrit :
> Hervé
> When will you set this value? During release:prepare and modify the pom?
> 
> Enrico
> 
> Il sab 28 set 2019, 17:55 Hervé BOUTEMY <herve.bout...@free.fr> ha scritto:
> > 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: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org





---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Reply via email to