This ended up being good advice. The problem was an antique maven-install-plugin specified in a parent pom.
Is there some way to require minimum plugin versions in a custom packaging or its LifecycleMapping? thanks david jencks On Mar 21, 2011, at 3:06 AM, Benjamin Bentmann wrote: > David Jencks wrote: > >> Any advice? > > Provide a standalone example project that allows others to reproduce/analyze > the problem. > > > Benjamin > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
