I can't recall if this was supported in Maven 2 or not - that might be why. If it works there, then I agree with doing it. It would be best if they are filtered in from a property to make it easy to change though.
- Brett On 01/03/2011, at 8:45 AM, Lars Corneliussen wrote: > Hi, > > we should bind concrete versions of our plugins in the lifecycle definitions, > right? > > Sometimes maven starts to fetch super-old plugins (1.0.2) if the dependencies > are not explicitely set in the calling pom. We had to add a couple of > concrete bindings to npanday/dotnet/pom.xml for building on Maven 3, at least. > > Maven core also binds concrete plugin versions in their lifecycles for > jar/war/i.e. > > What do you guys think? > > -Lars -- Brett Porter [email protected] http://brettporter.wordpress.com/
