> I understand that maven has a default set of lifecycle plugins > (compile/test/install/deploy/etc). But I know people won't like the > fact that they'll have to ask or resort to an internal wiki to find out > how to build up a deployable package.
That's the beauty of Maven... All projects are built with "mvn compile". All projects are tested with "mvn test". All projects are installed into your local repo with "mvn install". All projects are deployed with "mvn deploy". In ant, you could easily have different targets for the same task in different projects, so you have to depend on ant to tell you what targets are available, then the user needs to have some intelligence to figure out which target does what unless it is really obvious by the name or documented somewhere. Maven standardizes this process. Wayne
