You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I believe the "validate" phase of Maven would be more appropriate to tie the plugin to, rather than "verify". "verify" is to check the integrity of the generated artifact (i.e. JAR file) at the end of the build, whereas "validate" is to validate the project before the build starts.
Thanks!
The text was updated successfully, but these errors were encountered:
Hi @nguillaumin, using verify by default is a result of a thorough discussion at one of my former teams. My colleagues strongly prefered performing these checks after running the tests. The present default is thus intentional and I do not incline to change it at this time.
If you do not like the default, you can change the phase easily in the pom.xml of our project.
Hi,
I believe the "validate" phase of Maven would be more appropriate to tie the plugin to, rather than "verify". "verify" is to check the integrity of the generated artifact (i.e. JAR file) at the end of the build, whereas "validate" is to validate the project before the build starts.
Thanks!
The text was updated successfully, but these errors were encountered: