dashorst opened a new issue, #1941: URL: https://github.com/apache/wicket/issues/1941
Rebuilding a Wicket release from its source tag should produce the same bytes as the artifacts on Maven Central, so anyone can verify that a published jar was built from the published source. Nobody has checked whether that holds today. [WICKET-7090](https://issues.apache.org/jira/browse/WICKET-7090) set `project.build.outputTimestamp` in the root pom, so archive entries carry a fixed timestamp instead of the build time. That is the prerequisite, not the whole job. What remains: - Build twice and compare (`mvn clean install -DskipTests`, then `mvn clean verify -DskipTests artifact:compare`) and list what differs: jars, OSGi manifests, javadoc and sources jars, the minified JavaScript, the examples war. - Fix each difference in the build. - Make sure every release sets `project.build.outputTimestamp` to its own date. - Consider registering Wicket at [Reproducible Central](https://github.com/jvm-repo-rebuild/reproducible-central), so releases are rebuilt and checked independently. -- 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]
