repository - Need presentation materials for convincing a customer to use Maven -


my customer needs more organized inventory of 3rd-party libraries (such jar files) used in production projects. involved number of java-based projects. inventory has not been consistently maintained in past , time has come account libraries being used (there quite few!) , enforce structured process introducing new libraries build environment.

i have tried pitching idea of using maven , artifactory in build process leverage tools' ability manage repository of binary libraries , handle transitive library dependencies. customer resistent suggestion because think create more work them maintain artifactory server , learn basics of maven.

currently, java projects built using ant scripts. transitive dependencies largely managed trial-and-error. inventory of libraries in use maintained hand , binaries stored in subversion repository. customer recognizes needs improved, current suggestions improvement involve more ad-hoc "manage hand" approaches.

i want convince customer combination of maven , artifactory viable off-the-shelf solution java library management needs. can direct me literature/materials can use create presentation customer on features , strengths of maven , artifactory?

any other arguments/suggestions/etc assist me in appreciated.

i want convince customer combination of maven , artifactory viable off-the-shelf solution java library management needs.

as pointed out in comment, customer doesn't need adopt maven benefit dependency management, adapt existing ant scripts use maven ant tasks or ivy. might less scary , remove pain.

regarding way maven manages dependencies, explain that:

  • an artifact identified coordinates (groupid, artifactid, version).
  • this allows store store them using standardized directory structure (a repository)
  • a dependency more jar: it's jar pom enables things transitive dependencies resolution.

and benefits of such dependency management solution are:

  • no mess dependencies, uniquely identified (no more "what version that?" syndrom)
  • no more binary data in vcs (faster checkout, less space)
  • easier reuse of artifacts between projects (no more jars sent email)
  • easier management transitive dependency resolution

and because don't want rely on public repositories, because need store own artifacts, need enterprise repository. personal choice nexus:

  • because it's file based (unlike artifactory, , don't want put artifacts in database)
  • because it's simple install/use
  • because it's easy administrate

here resources nexus (sorry, don't use artifactory):

and in case, here presentation material maven:


Comments

Popular posts from this blog

ASP.NET/SQL find the element ID and update database -

jquery - appear modal windows bottom -

c++ - Compiling static TagLib 1.6.3 libraries for Windows -