Hi Herve, I want to make sure we understand correctly. So. What you want to achieve with this property is to stick the property to one fixed value when the user has supposed the archive would have same content. And opposite, means that the property would be real when the content of the archive should change.
That's technically ok that the plugins are aware of shared time stamp, but this looks like the problem with egg and chicken. Practically, the user would never be sure when is the time that the time stamp should be fixed value. Not sure if the user would be able to have fully working reproducible build. Perhaps the users will have exactly this question too. Cheers Tibor17 On Sat, Oct 5, 2019 at 7:52 PM Hervé BOUTEMY <herve.bout...@free.fr> wrote: > based on the feedback I got, I updated the proposal: > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=74682318 > > The archives entries timestamp is now configured with > project.build.outputTimestamp property, in ISO-8601 format > <project> > <properties> > > <project.build.outputTimestamp>2019-10-02T08:04:00Z</project.build.outputTimestamp> > </properties> > </project> > > The shared components, plugins, parent poms and Maven core branches have > been updated to match this new proposal > > > If no one objects, next week-end, I'll start the (heavy) release train to > bring (binary) Reproducible Builds plugins to general availability > > Regards, > > Hervé > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
