I wouldn’t expect too much from Maven 3. The people behind the Maven pedigree of build tools have always held the assumption that project builds are homogeneous, that is: all build problems fundamentally boil down to the same problem. This view of the world can be held fairly consistently in the face of opposing views but comes at a cost. The absence of scripting logic in Maven (“when you want to script you know you’re doing something wrong”), the cumbersome plugin API (“no ordinary Maven user should want to write a plugin”) and the central repository (“we all have the same dependencies”) are all testaments of this overarching assumption.
In the real world build problems are heterogeneous because people build software for a wide variety of reasons. They all ‘develop’ like we all ‘drill holes’ once in a while for solving unique problems. Regardless of your level of abstraction you’ll always find similarities when comparing arbitrary build problems. It is the reveration of these similarities and the condemnation of differences that is the downfall for Maven’s design and the reason why it draws so much flak. Basically, Maven is authoritarian and utopian in its outlook.
PS: Maven has good features, like convention-over-configuration and the idea of using repositories (the Maven implementation of this idea is troublesome).