Only that the majority of users will get just get "unable to resolve artifact" errors, and probably never know that they can update aether - which, whilst it isn't a difficult thing to do is just a bit fiddly - instead they'll just get frustrated that once again "maven black magic sucks".
If rolling without 1.12 of aether, could we at least mention clearly in whatever release notes are blogged/emailed out that if they encounter such issues, they can be resolved with an Aether update. Still, I guess things could be worse - we could be using a build tool built on Ivy. On 20/08/2011, at 10:59 PM, Mark Struberg wrote: > If we release 3.0.4 now, a user might still update his local maven > installation to 1.12 easily. So I see no downside to the current status quo.
