Le jeudi 10 février 2022, 14:35:58 CET Delany a écrit :
> Thanks I'll send PR.
thank you for helping
> Since you ask, I think Maven should allow silencing any warning for any
> plugin, but that's for another day.
sure :)
>
> I'm not able to compare builds. I run `mvn clean install`, and `mvn
Thanks I'll send PR.
Since you ask, I think Maven should allow silencing any warning for any
plugin, but that's for another day.
I'm not able to compare builds. I run `mvn clean install`, and `mvn clean
package artifact:compare` and I get an error "could not find repository
with id = central"
If
Le mercredi 9 février 2022, 09:31:00 CET Delany a écrit :
> Hi Herve,
>
> I see you already check that the project.parent was part of the reactor and
> you don't issue the warning if it is.
> An edge case is the -rf switch. Even though you have the opportunity to
> change files, the sense is that
Hi Herve,
I see you already check that the project.parent was part of the reactor and
you don't issue the warning if it is.
An edge case is the -rf switch. Even though you have the opportunity to
change files, the sense is that it is the same build being resumed, so I
would also not warn in this
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
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
