This is not a comparison to other options, but from my perspective I would say standardization of code artifacts and structure, advanced dependency management, descriptive vs. programmatic builds, enforcement of enterprise conventions through super pom's, rich plugin ecosystem, project site that allows open visibility into build and build-related operations (testing results, code coverage, code quality, etc), integration into enterprise build and deployment tools.
Tony On 9/30/07, Marco Mistroni <[EMAIL PROTECTED]> wrote: > > hello all, > i am a big fan of maven (i have been using it since approx 3 years..).. > and i'd like to use it @ my work, > where we are still using ant and coding most of the tasks manually.. > but i'd need good arguments, as now many IDEs( especially IntelliJ) offer > lot of capabilities such > as code coverage, identifying code smells etc.... > so, i'd need good arguments for pushing for Maven2 @work.... > > can anyone help me out? > > thanks and regards >
