I do appreciate the help I have been given with the Maven pom.xml file. However what I would really need is for someone to create a pom.xml file that works perfectly and is something that the Maven team would be willing to accept. In addition I would need the community to work with the Maven team to submit the jar.

Right now having a broken pom.xml file is confusing to developers that want to run the project locally. So, with that I have decided to let go of the Maven pom.xml file and have removed it from the project. I am very happy with my Groovy build scripts and they work well.

I would be fine keeping the JMesa jar (currently 2.3.4) file on my GoDaddy site though and people are welcome to link to it.

This would be the repository declaration in your pom.xml.

<repositories>
    <repository>
        <id>jmesa</id>
        <url>http://jmesa.org/maven</url>
    </repository>
</repositories>

This would be the dependency declaration in your pom.xml.

<dependency>
   <groupId>jmesa</groupId>
   <artifactId>jmesa</artifactId>
   <version>2.4.1</version>
</dependency>

I put the JMesa Maven pom.xml file on the site and you can use it as a starting point if you want to try and get the JMesa jar file on the Maven repositories.