Le dimanche 29 septembre 2019, 16:54:04 CEST Emmanuel Bourg a écrit : > Le 28/09/2019 à 17:55, Hervé BOUTEMY a écrit : > > 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. > > It seems a bit odd to me to tie the build timestamp to the pom. The fact > that it could be inherited is disturbing, i.e. if you forget to override > it in a subproject your build time will be wrong. what does "wrong" or "right" mean? I know some solution for reproducible builds that blindly put zip entries timestamp to 1970-01-01
> > > WDYT? Any other idea? > > I thought the timestamp would rather go to a separate file deployed > along the pom and capturing the build environment. What Maven needs then > is a command line parameter to force a specific build time (and/or > support for the SOURCE_DATE_EPOCH environment variable). a separate file? oh no!!! please try Maven core branch reproducible and you'll see Maven native Reproducible Build in action https://github.com/apache/maven/tree/reproducible The timestamp was defined 4 days ago, and will remain defined for as long as nobody change it in git Regards, Hervé > > Emmanuel Bourg > > --------------------------------------------------------------------- > 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
