[
https://issues.apache.org/jira/browse/RAT-536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18066962#comment-18066962
]
Hervé Boutemy commented on RAT-536:
-----------------------------------
I'll dive into this more in depth a little bit later, but I get that the value
of the timestamp is visible in generated site, which triggered some concerns
because "it was not accurate"
I see 2 options:
1. either the value of timestamp is inherited from parent, instead of being
defined in project: we can define in the project, and have the timestamp
updated during release to match moment of the release
2. or disable the timestamp only in site, but not in build (as reproducible
output binaries are definitively a good thing, site is a different story): just
need to define the value in site plugin instead
https://maven.apache.org/plugins/maven-site-plugin/site-mojo.html#outputTimestamp
there are simple solutions, just need to make the best decisions based on what
Creadur team prefers
> RAT releases are not reproducible any more
> ------------------------------------------
>
> Key: RAT-536
> URL: https://issues.apache.org/jira/browse/RAT-536
> Project: Apache RAT
> Issue Type: Bug
> Components: build
> Affects Versions: 0.17, 0.18
> Reporter: Hervé Boutemy
> Priority: Major
>
> see reproducibility checks over releases:
> https://github.com/jvm-repo-rebuild/reproducible-central/blob/master/content/org/apache/rat/README.md
> regression was apparently introduced in
> https://github.com/apache/creadur-rat/commit/969f474e82aa7ef9082d1156d777b7e7b42ac3e3
> while working on RAT-397
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
