slachiewicz opened a new pull request, #878:
URL: https://github.com/apache/maven-shade-plugin/pull/878

   Fixes #679.
   
   `ApacheNoticeResourceTransformer` ended the copyright line of the generated 
NOTICE with the current year, so a shaded jar changed with the year it was 
built in. The mojo now passes the year of `project.build.outputTimestamp`, read 
in UTC from either format maven-archiver accepts, to every 
`ApacheNoticeResourceTransformer` that does not configure the new 
`copyrightYear`. Without a timestamp the current year is used as before; a 
value the mojo cannot parse logs a warning and falls back the same way.
   
   #860 takes the year from the timestamp of the first dependency NOTICE entry 
instead. That entry carries the dependency's build date, not this project's, so 
with `inceptionYear` 2024 and a dependency NOTICE stamped 2019 the line would 
read `Copyright 2024-2019`. The project's own reproducible timestamp avoids 
that.
   
   `setDefaultCopyrightYear` leaves an explicitly configured `copyrightYear` 
alone. #830 changes the same method in `ShadeMojo`, so whichever lands second 
needs a small rebase there.
   
   Verified: the new IT `apache-notice-output-timestamp` (outputTimestamp in 
2019) fails on `master`, whose NOTICE reads `Copyright 2006-2026`, and passes 
with this change; `-Prun-its verify` → 77 unit tests and 86 ITs pass.
   
   ---
   
   To make clear that you license your contribution under
   the [Apache License Version 2.0, January 
2004](https://www.apache.org/licenses/LICENSE-2.0)
   check one of the following:
   
   - [x] I hereby declare this contribution to be licensed under the [Apache 
License Version 2.0, January 2004](https://www.apache.org/licenses/LICENSE-2.0)
   - [x] I hereby declare that I have filed an [Apache Individual Contributor 
License Agreement](https://www.apache.org/licenses/icla.pdf).
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to