Hi, i wanted to join the crowd :) Maven1 was like some kind of magic to me back then, a sort of "deus ex machina". A "smart" ant (?). No "convention over configuration" stuff yelled, it was messy but it worked. It was kinda "nothing is unsolvable" but you got finally a huuge maven.xml -- and sure death. It was a nice "experiment" that these principle worked. Also, it's architecture was the reason for M1/M2 cut and breaking backward compatibility.
IMHO, Maven2 is great thing and it will unleash its real potential in near future. But remember, Maven2 is NOT just a "command line buld tool", it is (will be?) an INFRASTRUCTURE.... There was some comments before, like "Maven 2.0" should be degraded to BETA and not final... well, not quite. The core (maven itself, not remote repo contents) was always sound. Just run M2 in isolated environment with clean and properly filled POM's, without central and M2 will blow all your needs! The problems are somewhere around "producers" (who provides central repo content, NOT uploads it). And legacy artifacts. And... obviously out of power of few PMC member and commiter who works hard on M2. Many packages (eg. Sprinframework) does not have POM's in repo. M2 peoples cannot _make_ Spring team (another OSS team) to deliver POM when they AFAIK use Ivy... or something 3rd. We also had problems converting projects from M1 to M2 and Ant -> m2, and spent lot of hours with it. But most of the problems arised when some "unusual" things happened during builds. Those "hacks" where terrible, something like "put your left hand into right pocket", and it had nothing to do with M2 itself, It was merely bad design of build process or simply bad idea to it like that in original build.... So, switch before it gets too late! Have fun! ~t~
