You could always put it in a separate Maven project and declare a dependency
to that artifact for the exec plugin. But then it might be better to create
a Maven plugin instead...
If it's something simple, why not just write a Groovy script and use the
gmaven-plugin to execute it? You'll then keep
It is sometimes very convenient to have a java class with a main method used
to help build a maven project, but one that is so specific to that project
that it is too large of an overhead to author it as a reusable maven plugin.
Using maven-exec-plugin, the class can be run, but then the question
