[
https://issues.apache.org/jira/browse/MPOM-265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17378953#comment-17378953
]
Herve Boutemy commented on MPOM-265:
------------------------------------
bq. Wouldn't all Apache projects not setting/overriding this property be having
a problem?
no: they just don't control the timestamp value, which is just a fixed value
inherited from parent instead of a fixed value that is updated during their
release, nothing harmful
as I just wrote in MPOM-255, pom.xml is not the unique output, ASF official
release source-release.zip is done from this build: it is important to me that
it is reproducible
and with OS-specific newline from the release manager, and future build vs
consumer pom, the situation is not as trivial as it seems: reproducible builds
is really a picky beast, checking every fingerprint...
I don't have the one and unique truth, it's good to have a positive discussion
to make sure everybody everybody understands the impact of every choice
> re-enable reproducible builds for ASF parent POM source-release.zip
> -------------------------------------------------------------------
>
> Key: MPOM-265
> URL: https://issues.apache.org/jira/browse/MPOM-265
> Project: Maven POMs
> Issue Type: Bug
> Components: asf
> Affects Versions: ASF-24
> Reporter: Herve Boutemy
> Priority: Major
> Fix For: ASF-25
>
>
> project.build.outputTimestamp property was removed in MPOM-255
> need to add it back for ASF parent POM source-release zip file
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
