Hi Delany,
Good question: let's see if we can improve the message that I added in
MARTIFACT-28 [1]
First, remember that it's all about Reproducible Builds [2].
As described in the MARTIFACT-28 issue, inheriting the parent pom release
timestamp technically works (it gives a reproducible value to your current
build), but does not match the current release/build timestamp: you probably
prefer to have a timestamp defined in your reactor
= that is the message that we need to make as clear as possible
Don't hesitate to propose an updated message that fits inclusion in a plugin
output...
Notice that I'm surprised of your choice to set the outputTimestamp to $
{maven.build.timestamp}, given this value is not reproducible (if you build 2
time the same code, you'll get 2 different values), choosing this value defeats
the whole purpose of the configuration.
Remember, it's all about Reproducible Builds, and your objective is to run the
build 2 times and check you get the same binary output:
mvn clean install
mvn clean package artifact:compare
Regards,
Hervé
[1] https://issues.apache.org/jira/browse/MARTIFACT-28
[2] https://maven.apache.org/guides/mini/guide-reproducible-builds.html
Le mardi 8 février 2022, 11:04:33 CET Delany a écrit :
> Hi. Why does maven-artifact-plugin complain
>
> [WARNING] project.build.outputTimestamp property should not be inherited
> but defined in parent POM from reactor
>
> I never had a plugin complain about utilizing inheritance. Why does it care?
> When I add the line to the project the warning disappears
>
>
> <project.build.outputTimestamp>${maven.build.timestamp}</project.build.outpu
> tTimestamp>
>
> Thanks,
> Delany
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
