fietser97 commented on issue #13393: URL: https://github.com/apache/maven/issues/13393#issuecomment-6120212784
> 6\. this is Reproducible Builds activated by default (with the value you see) = > see https://maven.apache.org/guides/mini/guide-reproducible-builds.html for full description of the intent > if you want to disable that feature as a quick immediate solution, just add a `project.build.outputTimestamp` property to your `pom.xml` with a unique character value like `x` (or any other non-digit char) > if you want, you can also not disable it (as Reproducible Builds has interesting results), but for example define a value tied to last Git commit (as explain in FAQ): it's not something I personally think is optimal for Reproducible Builds, but it can be another approach > > This is a breaking change if you use this for your build pipeline. To get the newest version. > > > I'd be interested to understand precisely what it breaks for you: how do you recognize "the newest version"? > are you building SNAPSHOTs? or only releases? > what is "build-info" to you? how do you get visibility into it? We build both snapshot and releases. We get the information in our artifact store and when that store sees a build year of 1980 in the artifact. It tells us no. Because it's too old. Also, when we deploy our applications we validate both the version number, start time and build time of artifact when it comes to releases. Which now contain that same date. So for us the it breaks because the date is way too old. -- 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]
