First, treating build as a separate discipline from code is, in my experience, a recipe for trouble. The poms or build.xml or whatever files are just as much part of the source code as the java. Someone may own Jenkins or whatever, but the devs should own the building of the code they write.
Second, the environmental impact of Maven depends critically on the nature of the code. If your entire build is composed of compiling Java code and delivering jar files, the poms are trivial and the Maven cost is near-zero. If, on the other extreme, you insist on fighting with Maven and having policies for dependencies, or releases, or whatever, that require extensive 'negotiation', it's a very different picture. In between, if you have significant custom build activity (e.g. code generators), you might need some of your own plugins. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
