Yes, having the timestamp to 0 is something I wanted generally to avoid. But this has opened another question: use what value? Can this be automated?
I knew that war files could be a specific use case. Perhaps this plugin requires a specific way of handling reproducibility, even more than the standard in the proposal "define a timestamp in pom.xml"? Do you want that I create a Reproducible branch in mave-war-plugin like I did for Jar, Source and Assembly, so we can test? Regards, Hervé Le samedi 5 octobre 2019, 22:19:54 CEST Vladimir Sitnikov a écrit : > >but > >who really looks at the timestamp of entries in release zips/jars/tar.gz > >honestly? > > Tomcat when it decides on what to send in the "Last-Modified" header. > For instance, current Gradle does not allow to configure the timestamp, and > for reproducible builds it always sets the timestamp to 0 or so. > It breaks Tomcat's assumptions: > https://github.com/gradle/gradle/issues/10917 > > Vladimir --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
