[maven-site] branch master updated: introduce artifact:check-buildplan

[hb...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

hboutemy pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven-site.git


The following commit(s) were added to refs/heads/master by this push:
     new ca12a2f6 introduce artifact:check-buildplan
ca12a2f6 is described below

commit ca12a2f6fe9351686e112de4fe7d77b0639efa5a
Author: Hervé Boutemy <hb...@apache.org>
AuthorDate: Thu Apr 7 08:08:20 2022 +0200

    introduce artifact:check-buildplan
---
 .../apt/guides/mini/guide-reproducible-builds.apt  | 23 ++++++++++++++++------
 1 file changed, 17 insertions(+), 6 deletions(-)

diff --git a/content/apt/guides/mini/guide-reproducible-builds.apt b/content/apt/guides/mini/guide-reproducible-builds.apt
index cf75c7ef..3895436b 100644
--- a/content/apt/guides/mini/guide-reproducible-builds.apt
+++ b/content/apt/guides/mini/guide-reproducible-builds.apt
@@ -41,8 +41,11 @@ Configuring for Reproducible Builds
 
  There is no Maven version prerequisite. Everything happens at plugin level:
 
- [[1]] Upgrade your plugins to reproducible versions, particularly <<<maven-jar-plugin>>>, <<<maven-source-plugin>>>,
- and <<<maven-assembly-plugin>>> to version 3.2.0 minimum.
+ [[1]] Upgrade your plugins to reproducible versions: to easily detect {{{/plugins/maven-artifact-plugin/plugin-issues.html}required upgrades}}, run
+ 
+--------
+mvn artifact:check-buildplan
+--------
 
  [[2]] Enable Reproducible Builds mode for plugins, by adding <<<project.build.outputTimestamp>>> property to the project's <<<pom.xml>>>:
 
@@ -61,15 +64,23 @@ Configuring for Reproducible Builds
  Using {{{/plugins/maven-artifact-plugin/compare-mojo.html}<<<maven-artifact-plugin>>>'s <<<compare>>> goal}},
  you can check that the second build of your project produce the same output than an initial build:
 
- [[1]] build and <<<install>>> your project: <<<mvn clean install>>> (don't hesitate to customize arguments to better match your project)
+ [[1]] build and <<<install>>> your project (don't hesitate to customize arguments to better match your project):
+ 
+--------
+mvn clean install 
+--------
 
- [[2]] rebuild (<<<verify>>> only, without installing) and check against the previous install: <<<mvn clean verify artifact:compare>>>
+ [[2]] rebuild (<<<verify>>> only, without installing) and check against the previous install:
+ 
+--------
+mvn clean verify artifact:compare
+--------
 
  []
 
 * How to fix my Maven build reproducibility?
 
- If something is still not reproducible after initial setup:
+ If something is still not reproducible after initial setup and {{{/plugins/maven-artifact-plugin/plugin-issues.html}automatic check from <<<artifact:check-buildplan>>>}}:
  
  [[1]] Use {{{https://diffoscope.org/}diffoscope}} to find the unstable output between builds. The <<<artifact:buildinfo>>> goal proposes a command with path to files: just copy/paste to launch.
   
@@ -108,7 +119,7 @@ Configuring for Reproducible Builds
    * if you have a custom release process tooling, you'll need to add the feature to your release tooling.
      Notice that if you're using <<<versions-maven-plugin>>> in custom release scripts, starting with release 2.9.0, {{{https://github.com/mojohaus/versions-maven-plugin/issues/453}<<<versions:set>>> goal updates the property}}.
 
-   * instead of explicitely writing a timestamp in their <<<pom.xml>>>, some people tend to prefer using last Git commit timestamp, like <<<${git.commit.time}>>> from
+   * instead of explicitely writing a timestamp in their <<<pom.xml>>>, some people tend to prefer using last Git commit timestamp, like <<<$\{git.commit.time}>>> from
    {{{https://github.com/git-commit-id/git-commit-id-maven-plugin}git-commit-id-maven-plugin}}.
 
   []