Use the Maven Versions Plugin to show the latest versions of all the
plugins you have specified. Most of the time the latest are the
greatest. I only move back if I hit specific bugs (or I move forward
if a patch is available, and make my own release)
http://mojo.codehaus.org/versions-maven-plugin
On 14/06/2010, Jason van Zyl wrote:
> All plugins because unfortunately we haven't had the best track record with
> respect to behavioral compatibility between releases.
OK, thanks.
What about the Maven Available Plugs list at [1] - can one assume that
these plugin versions will work together O
All plugins because unfortunately we haven't had the best track record with
respect to behavioral compatibility between releases.
On Jun 14, 2010, at 1:37 PM, sebb wrote:
> The guide to configuring plugins [1] says that:
>
> "Important Note: It is recommended to always defined each version of
>
The guide to configuring plugins [1] says that:
"Important Note: It is recommended to always defined each version of
the plugins used by the build to guarantee the build reproducibility."
This seems sensible, but I've also been told that one should not
specify the versions of the core plugins [2]
