Can anyone help answer whether I've missed some subtlety as to why a
fix like this wouldn't work (I appreciate the inner workings of maven
can be a bit complicated...) ?
On Sun, Feb 3, 2008 at 6:10 PM, Nigel Magnay [EMAIL PROTECTED] wrote:
The problem is that putting it in pluginManagement
This is fixed in 2.1, but if you are constantly having this problem, it
sounds like maybe you need to use pluginManagement in a corp pom to
resolve this issue.
-Original Message-
From: Nigel Magnay [mailto:[EMAIL PROTECTED]
Sent: Sunday, February 03, 2008 8:44 AM
To: dev@maven.apache.org
The problem is that putting it in pluginManagement doesn't help
because the builds genuinely do want to use different versions,
particularly of internally-developed mojos that change in different
(and sometimes incompatible ways).
A typical case is a base library uses a fixed, stable release, but
