Hi folks,

This may be of general interest, at least I had no idea about the consequences.
So I thought I’d share the result of my research.

> Am 06.01.2022 um 10:30 schrieb Thomas Vandahl <t...@apache.org>:
> 
>> Maybe somebody else knows how that can happen.
> The effective POM shows the following entry:
> <project.build.outputTimestamp>2020-01-22T15:10:15Z</project.build.outputTimestamp>
> 
> Now we see why the year number in NOTICE is wrong. But who sets this?

Found it. For the information of all interested parties, the following command

    mvn org.apache.maven.plugins:maven-help-plugin:3.2.0:effective-pom 
-Dverbose=true

produces the line (among others)

    
<project.build.outputTimestamp>2020-01-22T15:10:15Z</project.build.outputTimestamp>
  <!-- org.apache:apache:23, line 95 —>

which actually is true. See 
https://search.maven.org/artifact/org.apache/apache/23/pom

This entry causes different things to happen to the build artifacts, for 
example a fixed last-modified-date for all Jar entries:
—8<—
...
  7743 Wed Jan 22 15:10:16 CET 2020 
META-INF/maven/org.apache.commons/commons-jcs3-core/pom.xml
    68 Wed Jan 22 15:10:16 CET 2020 
META-INF/maven/org.apache.commons/commons-jcs3-core/pom.properties
...
—8<— 

Or the Javadoc files, respectively:
—8<—
...
 10046 Wed Jan 22 15:10:16 CET 2020 overview-frame.html
 17979 Wed Jan 22 15:10:16 CET 2020 overview-summary.html
131038 Wed Jan 22 15:10:16 CET 2020 overview-tree.html
...
—8<— 

So unless you explicitly set the property project.build.outputTimestamp on your 
own, all your artifacts will derive it from the Apache Parent POM.

Recent example:
—8<—
...
 15417 Wed Jan 22 15:10:16 CET 2020 
META-INF/maven/commons-cli/commons-cli/pom.xml
    57 Wed Jan 22 15:10:16 CET 2020 
META-INF/maven/commons-cli/commons-cli/pom.properties
...
—8<—

Obviously, this has to do with 
https://maven.apache.org/guides/mini/guide-reproducible-builds.html 
There it is mentioned that the maven-release-plugin 3.0.0-M1 and later is 
supposed update the property (which it doesn’t as we see).

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

Reply via email to