miskr-instructure commented on issue #13393: URL: https://github.com/apache/maven/issues/13393#issuecomment-6171235333
> TBH, I think it is not. As if you rebuild same tag today, and one year after, you get the same resources but with 1 year difference, that end up as their Last-Modified IIUC, while resources are unchanged. > With RB enabled, when you rebuild same tag, you'd end up with same timestamp, no matter did rebuild happen one month or one year after. Do you mean we should explicitly set the `outputTimestamp` (to a real value, ever increasing between releases) and not use the default? Ie. for release N we would use 2026 March 1, then for release N+1 we would be expected to use another, larger `outputTimestamp`? That would achieve the reproducible thing you mention, where we could rebuild release N in August with the timstamp set to the same value as it was originally (2026 March 1). If this is the expectation from the users of maven, to me it would make more sense **to force people to supply a timestamp and not default at all** (accepting explicit "-" or some other symbol to disable the behavior). That would probably annoy people too much in a minor release though, but _defaulting_ to 1980-02-01 doesn't make too much sense to me. -- 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]
