maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dan Tran <>
Subject Re: Skill set to maintain a enterprise build system using Maven
Date Mon, 01 Jun 2015 00:10:41 GMT
For my case, I am very fortunate to involve with the the product from early
day (a year ba ck) and Maven is embraced to the max where plugins are
developed to solve every build use case in a full dev/qa/releng integration
pipeline. The developments are multi-sites and  heavily depending Maven
Central like repository cluster and Maven release plugin.

The odd thing to me is it is hard to find Java talent with a passion for
build/ci with Maven, and it is also  hard to switch perl/python devops into
java to maintain Maven build.  am I wrong here?



On Sun, May 31, 2015 at 3:16 PM, Benson Margulies <>

> 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:
> For additional commands, e-mail:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message