The automvn lifecycle merges the GNU autoconf lifecycle with Apache maven project automation. Autoconf does not deal with transitive dependencies and project release websites like maven does so the extended maven project lifecycle is added to autoconf for those undefined areas. For instance, if your project has a dependency on rrdtool, autoconf does not try to satisfy that dependency, but automvn will. Autoconf is used underneath maven since maven is a lifecycle management tool with no non-java build tools.
This lifecycle is for developers with source code commit access and the ability to release a new version of the project so patching is not needed.
Document written May 17, 2009.
run autoreconf on project
make dummy jarfile
|install||install artifacts to repo|