Le dimanche 6 octobre 2019, 16:41:27 CEST Emmanuel Bourg a écrit : > Le 06/10/2019 à 09:43, Hervé BOUTEMY a écrit : > > Notice that you can also express a timezone (as digits), as seen in the > > unit tests. > I know but that's not desirable, otherwise the formatted timestamp would > depend on the timezone of the developer no, it does not add any dependency on developer configuration: 2019-10-05T18:37:42Z == 2019-10-05T20:37:42+02:00 == 2019-10-05T16:37:42-02:00
> and that would harm the > reproducibility of the pom (I assume the timestamp is added > automatically to the pom during the build, is that right?). when will this value be written in the pom.xml is independant: currently, in my PoC, I wrote the values by hand. In the future, it will probably be updated by maven-release-plugin, and we'll have to choose if the timestamp is written in Z or if it is written in local timezone with its offset: both ways of expressing the timestamp are valid and will give reproducible result > > >> Would it be possible to prevent this property from being inherited? > > > > AFAIK no. > > And I find that default inheritance from parent to child is a nice > > feature. > > Why do you think this is a nice feature? I can only see the downside of > child projects having a timestamp clamped in the past and leaving the > developers clueless about the reason. This would be especially bad if a > widely used parent pom like org.sonatype.oss:oss-parent or > org.apache:apache had it. once again, war files taken apart for web servers, who looks at timestamp in zip files? > > 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
