[
https://issues.apache.org/jira/browse/RAT-536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18066965#comment-18066965
]
Hervé Boutemy edited comment on RAT-536 at 3/20/26 7:28 AM:
------------------------------------------------------------
looking at site: https://creadur.apache.org/rat/index.html "Last Published:
2025-10-12| Version: 0.17"
do you prefer the "Last Published" value be when the release was done? or when
the site was generated?
at release time, this will be the same, it's only when built NOT at release
time that they differ (either when someone rebuilds from tag = where we try to
get reproducible output, or when someone builds site of a SNAPSHOT)
looking at website history, I see that with previous 0.16.1 version, the site
was ... uh... not up to date:
https://web.archive.org/web/20240810175539/https://creadur.apache.org/rat/index.html
I get why you did RAT-397 :)
I see also that RAT's pom.xml did not define its timestamp, but just inherited
from parent, so its value was the time of release of the parent POM, not from
RAT
if you define a real value in your pom.xml (instead of "a"), you'll get the
value updated at RAT release time (by Maven Release Plugin): so the value will
be accurate at the time of release = what we do by default
would that be sufficient for you?
(I advise doing that step, whatever you choose from a site perspective: getting
timestamp from RAT release in jars and zips is a good idea)
in addition, if you still prefer having a site with moving (non reproducible)
"when built by someone" timestamp, the configuration in site plugin can be done
in addition
was (Author: hboutemy):
looking at site: https://creadur.apache.org/rat/index.html "Last Published:
2025-10-12| Version: 0.17"
do you need the "Last Published" value be when the release was done?
or when the site was generated?
looking at website history, I see that with previous 0.16.1 version, the site
was ... uh... not up to date:
https://web.archive.org/web/20240810175539/https://creadur.apache.org/rat/index.html
I get why you did RAT-397 :)
I see also that RAT's pom.xml did not define its timestamp, but just inherited
from parent, so its value was the time of release of the parent POM, not from
RAT
if you define a real value in your pom.xml (instead of "a"), you'll get the
value updated at RAT release time (by Maven Release Plugin): so the value will
be accurate at the time of release = what we do by default
would that be sufficient for you?
(I advise doing that step, whatever you choose from a site perspective: getting
timestamp from RAT release in jars and zips is a good idea)
in addition, if you still prefer having a site with moving (non reproducible)
"when built by someone" timestamp, the configuration in site plugin can be done
in addition
> 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)
