Hi Curtis,
On 4/16/15 8:29 PM, Curtis Rueden wrote:
Hi Karl,
The Apache Maven team is pleased to announce the release of the Apache
Maven Verifier Plugin, version 1.1
Congratulations on the release.
Thanks..
> Out of curiosity, I was wondering...
What is the purpose of the maven-verifier-plugin, compared to the
maven-enforcer-plugin? From the Verifier plugin's web site, it sounds very
much like a specific enforcer rule: fail the build if these particular
resource files are not found. Or am I missing some critical distinction
there?
The only differences at the moment is that you can check the content of
files with maven-verifier-plugin...and may be we integrate the rest
which is not provided by maven-enforcer-plugin into it...
Furthermore, after doing a web search for "maven verifier enforcer", the
first hit is actually the maven-enforcer-plugin's Usage page:
http://maven.apache.org/enforcer/maven-enforcer-plugin/usage.html
Where it gives a specific example that flags the maven-verifier-plugin as a
banned plugin (!!!), and suggests to use the maven-invoker-plugin instead.
I know it was only a theoretical example, but the implication is that the
XML snippet has some grounding in reality somehow...
So I was wondering if there is a writeup anywhere with "best practice"
recommendations concerning these plugins? Comparison, pros & cons, etc.? In
a nutshell: I had not heard of the Verifier plugin before your
announcement, and was wondering what use cases it covers that the enforcer
plugin does not also cover.
I think the maven-verifier-plugin will be retired in the (not so far )
future...I have made a final Maven 2.2.1 compatible version as the last
one...to get a final clean release line...
https://builds.apache.org/job/dist-tool-plugin/site/dist-tool-prerequisites.html
Kind regards
Karl Heinz Marbaise
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
