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
