I agree with that....from CVS to SVN shouldn't be to difficult, interaction
with SVN is a positive step forward, most other opensource projects are
already on SVN.
As far as Ant to Maven, this one will be a little more of a learning curve
if one is not familiar with Maven. One thought is to support both for a
period of time until everyone is comfortable. Maven is not a do or die type
decision either, if most people don't want it then we don't switch. As Jason
mentioned in an earlier post this week you can indeed do everything with Ant
that you do with Maven. I would at least like to see us publish to the maven
repository. In any case I have listed a few reasons I prefer maven below.
Benefits of Maven:
1. Provides a standard directory structure and deploy/test mechanism that is
pretty well known.
2. Out of the box support for snapshot creation, versioning etc...
3. Although maven and ant provide similar functionality, with maven you
don't have to maintain huge build scripts.
4. Maven makes it easy to support multiple ide's (or at least most of the
popular ones. eclipse, intelliJ and Netbeans) without maintaining IDE
specific files in the JSFT source tree.
5. Maven has many plug-ins to do common build, deployment and generation of
project metrics.
6. central online repository means that the jars we use to build are the
same jars others use to build, the plug ins we could use to generate code
coverage reports, unit test reports etc.., are the same others would use to
generate reports.
7. know longer need to maintain the jars as part of the source repository.
(at least in most cases), this makes easier it to update dependencies etc..
8. built in support for generating project documentation that's integrated
with your build process.
9. massive support, many opensource projects use maven
Con:
1. learning curve.
? others?.....Im tainted I like maven, so please feel free to add some more
con's
On 6/2/07, Ken Paulsen <Ken.Paulsen_at_sun.com> wrote:
>
>
> Yes, we need to make sure the process is simple... and if we change
> there is a good reason for the change. There are some good reasons that
> have been mentioned, but we haven't discussed them fully. I plan to
> open this discussion at the developer meeting next week. My only
> requirement is that it be as simple as possible. :)
>
> Ken
>
> Michael Phoenix wrote:
> > So we're going to migrate from CVS to SVN and then from Ant to Maven?
> > If we constantly change the environment supporting JSFT development,
> > we're going to make it difficult to get any development done. Also,
> > learning new tools and technologies gets really ugly when you
> > constantly change the support environment. It's frustrating to just
> > start getting comfortable with a particular tool and then have to
> > learn another every time you turn around.
> >
> >
>
--
Frederick R. Brock
frederick.brock_at_gmail.com