I can tell you one thing. That POM seems to have an awful lot of explicit file directory references. Maven doesn't like that and it reduces the chance that one of Maven's major strengths can be exploited. An ideal Maven project can be cleaned, ZIPped and sent to a completely new system on the other side of the planet then rebuilt exactly with only an installed JDK and copy of Maven. It should not require or assume any files or directories external to the project itself. Maven should be allowed to build into its standard build areas (in the target directory) without being told via symbolic substitution. Maven isn't Ant and works very differently than Ant.
Beyond that, this appears to be a multi-language build. For that, I'd recommend something more like Gradle, which, unlike Maven is not as focused on Java and Java alone.
Some people, when well-known sources tell them that fire will burn them, don't put their hands in the fire.
Some people, being skeptical, will put their hands in the fire, get burned, and learn not to put their hands in the fire.
And some people, believing that they know better than well-known sources, will claim it's a lie, put their hands in the fire, and continue to scream it's a lie even as their hands burn down to charred stumps.
Thanks for your answer Tim.
Unfortunately I am not in the position to choose which build tool I want to use. I am not a programmer and I am not changing the code, I only need to get a WAR file from Maven and deploy it on Tomcat.
Always! Wait. Never. Shut up. Look at this tiny ad.
SKIP - a book about connecting industrious people with elderly land owners