Skip to content

build: drop repetitive comment on project.build.outputTimestamp #1095

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
psxjoy merged 3 commits into from
Sep 11, 2026
+2 −6
Merged

build: drop repetitive comment on project.build.outputTimestamp #1095

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
d3a37e2
build: drop repetitive comment on project.build.outputTimestamp
alaahong Sep 11, 2026
9e4ce30
docs: trim reproducible-build note in release guides
alaahong Sep 11, 2026
9a3d27d
docs: use official maven.apache.org link for reproducible builds
alaahong Sep 11, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 0 additions & 4 deletions pom.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -81,10 +81,6 @@ under the License.
<properties>
<revision>2.1.0-incubating</revision>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
<!-- Fixed build timestamp for reproducible builds (see https://maven.org.cn/guides/mini/guide-reproducible-builds.html).
apache-jar-resource-bundle derives the JAR NOTICE copyright end-year from this value; keep it in the same
year range as the release so the NOTICE shows a correct, non-inverted range (e.g. "2025-2026"). Update it
to the current release branch's creation time in every release so each build produces identical artifacts. -->
<project.build.outputTimestamp>2026-09-10T00:00:00Z</project.build.outputTimestamp>
<java.version>1.8</java.version>
<maven.compiler.target>1.8</maven.compiler.target>
Expand Down
2 changes: 1 addition & 1 deletion website/community/release/release-version.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -316,7 +316,7 @@ For example, to release version `2.0.0-incubating`, follow these steps:

- Create a new branch `2.0.0-incubating` as the release branch.
- Update the version number in `pom.xml` to `2.0.0-incubating`.
- Set the `project.build.outputTimestamp` in `pom.xml` to a fixed ISO-8601 timestamp (e.g., the release branch creation time) to ensure [reproducible builds](https://maven.org.cn/guides/mini/guide-reproducible-builds.html). If it is left empty, every build records a different timestamp, which does not satisfy reproducible-build requirements.
- Set a fixed `project.build.outputTimestamp` in `pom.xml` to ensure [reproducible builds](https://maven.apache.org/guides/mini/guide-reproducible-builds.html).
- Push the RC (Release Candidate) version tag.

```bash
Expand Down
2 changes: 1 addition & 1 deletion ...-cn/docusaurus-plugin-content-docs-community/current/release/release-version.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -316,7 +316,7 @@ svn ci -m "add gpg key for xxx"

- 创建一个新分支`2.0.0-incubating`作为发布分支
- 修改 `pom.xml` 中的版本号为 `2.0.0-incubating`
- 将 `pom.xml` 中的 `project.build.outputTimestamp` 设置为固定的 ISO-8601 时间戳（例如发布分支的创建时间），以保证[可复现构建](https://maven.org.cn/guides/mini/guide-reproducible-builds.html)。如果留空，每次构建的时间戳都会不同，不满足可复现构建的要求
- 在 `pom.xml` 中设置固定的 `project.build.outputTimestamp`，以保证[可复现构建](https://maven.apache.org/guides/mini/guide-reproducible-builds.html)
- 推送 RC(Release Candidates) 版本标签

```bash
Expand Down
Loading