Don't just dump a pom.xml file in the top directory with no other documentation than a LICENSE.txt. You're lucky I even know that pom.xml refers to Maven at all, and it's only by a miracle that I know I need to type "mvn" rather than "maven" to run maven.
I'm somewhat reasonably intelligent so I assumed I was going to type the mvn command followed by some optional build targets, so I did some reasonable things to find documentation of those build targets. There was no documentation in the downloaded package, nor does documentation appear to exist on the website. Thus far, this is the developer's fault.
So, I just ran a straight mvn. I got an error that I need to specify a build target (a "goal" in maven parlance), with a suggestion that I try "install," which is scary. That's it.
Apparently if I want to know what build targets are available, I'm going to have to look at pom.xml myself. The whole point of XML is to make files which are easy for software to read. So mvn ought to do this for me. I don't know how to read pom.xml; I've never read it in my life, and to be honest I need to spend my time learning ant's xml format for my job, thank you very much. And when I do discern what build targets are available, odds are I'll have no pointers as to which are standard, which are rare options, which are old unsupported junk, etc.
Take advantage of XML and tell me what's in it.