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
David Jencks wrote:
Is there some way to require minimum plugin versions in a custom packaging or
its LifecycleMapping?
No, lifecycle mappings can only provide default plugin versions, the
versions from the POMs win.
Benjamin
One of the nice side effects of moving the maven resolution code away from
apache is that people who work for companies with IP policies need additional
approval to look at the source to find out how it works. Since I don't have
such approval I'm really hoping for some advice.
I've been
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,
On Mon, Mar 21, 2011 at 6:06 AM, Benjamin Bentmann
benjamin.bentm...@udo.edu wrote:
David Jencks wrote:
Any advice?
Provide a standalone example project that allows others to reproduce/analyze
the problem.
People that can't browse source without approval likely can't post
code with out
