I agree with the incremental approach. One of the first things I did in introducing Maven to my current client is to just set it up to generate site. I started on my PC and generated site to it, sharing a "file://" URL for others to use the HTML pages. The value of all the reference docs (Javadoc, xref, FAQs), automated code review results, JUnit results, and Cobertura results became apparent fast, and affected process and standards change - in a very good manner.
Since your customers think they are happy with the current build setup, I suggest you generate site first and get that part of the process. Then work on having Maven correctly build the distributables too, and ease into that as site is accepted. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 24, 2005 11:59 AM To: Maven Users List Subject: Re: Introducing Maven to developers Concerning Argument 1: If you can't get them to see the value then you may want to use an incremental approach. This will involve more work on the front end for you though... Instead of changing the structure of their source, you can create a maven/ant script that will download the source and place it into your current directory (on Windows it might be c:\myMavenArea) into a directory structure that maven likes( c:\myMavenArea\projectName\src\main\java\com... ) . Then perform the build as you normally would with maven. That way, you can create the build and show them the value of using Maven without changing any or their source or their existing ant scripts. If you want, you could then hold a "lunch time learning" session about Maven and show them the massive and complex current ANT scripts compared to the comparitivley small Maven script as well as the other nice project management features you get for free using the maven plugins... Colin Chalmers <[EMAIL PROTECTED]> wrote on 08/24/2005 12:18:25 PM: > > 1. By splitting the project up into a number of small sub-projects > it's going to make it more difficult for the developers to work on the code. > Currently everything is in one CVS project which can easily be checked > out using Eclipse. How do others deal with this? By working with > different sub-projects in IDE or checking out all into one self-made > project (within IDE)? > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
