Grokbase Groups Maven users May 2006
FAQ

[m2] Continuum or CruiseControl as a CI server ?

Sebastien Arbogast
May 3, 2006 at 11:28 pm
I'm trying to find the best CI tool for a brand new Maven2-built project and
I'd like to have your experience feedback about which one to choose between
Continuum and CruiseControl.
I know that, as Continuum is a spin-off of Maven project it should be better
integrated with it. But on the other hand, CruiseControl seems more mature
to me, even if, to be honnest, I haven't tried any of them in a real
situation yet. That's why I need something more concrete. Is there any Maven
2 cruisecontrol plugin somewhere as there was one for Maven 1 ? What do you
think ?

--
Sébastien Arbogast

The Epseelon Project : http://www.epseelon.net
Blog : http://sebastien-arbogast.epseelon.net
TagSpot : http://www.tagspot.org
reply

Search Discussions

16 responses

  • Alexandre Poitras at May 4, 2006 at 2:53 am
    Well Continuum does the job for me, never thought about switching.
    What I like about continuum is that you can customize the goals
    invoked during a build (for instance, clean site:deploy deploy). I
    have never used cruise control but I heard it's hard to configure.
    On 5/3/06, Sebastien Arbogast wrote:
    I'm trying to find the best CI tool for a brand new Maven2-built project and
    I'd like to have your experience feedback about which one to choose between
    Continuum and CruiseControl.
    I know that, as Continuum is a spin-off of Maven project it should be better
    integrated with it. But on the other hand, CruiseControl seems more mature
    to me, even if, to be honnest, I haven't tried any of them in a real
    situation yet. That's why I need something more concrete. Is there any Maven
    2 cruisecontrol plugin somewhere as there was one for Maven 1 ? What do you
    think ?

    --
    Sébastien Arbogast

    The Epseelon Project : http://www.epseelon.net
    Blog : http://sebastien-arbogast.epseelon.net
    TagSpot : http://www.tagspot.org
    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
    For additional commands, e-mail: users-help@maven.apache.org
  • Kieran Brady at May 4, 2006 at 7:28 am
    We're using the latest CruiseControl with Maven 2 successfully - no problem
    configuring it. At the time I neeeded to implement a CI system back in
    October, Continuum wasn't mature enough and I couldn't realistically put it
    forward as an option as I couldn't get it to work :) I haven't tried
    Continuum since as CruiseControl has been happily doing multi-module builds,
    single projects, profiled builds, nightly builds running all reports, on
    demand builds and so on and so I've no reason to migrate.

    A couple of links:

    http://cruisecontrol.sourceforge.net/main/configxml.html
    http://jira.public.thoughtworks.org/browse/CC-363
    http://confluence.public.thoughtworks.org/display/CC/Home


    ----- Original Message -----
    From: "Alexandre Poitras" <alexandre.poitras@gmail.com>
    To: "Maven Users List" <users@maven.apache.org>
    Sent: Thursday, May 04, 2006 3:52 AM
    Subject: Re: [m2] Continuum or CruiseControl as a CI server ?


    Well Continuum does the job for me, never thought about switching.
    What I like about continuum is that you can customize the goals
    invoked during a build (for instance, clean site:deploy deploy). I
    have never used cruise control but I heard it's hard to configure.
    On 5/3/06, Sebastien Arbogast wrote:
    I'm trying to find the best CI tool for a brand new Maven2-built project
    and
    I'd like to have your experience feedback about which one to choose
    between
    Continuum and CruiseControl.
    I know that, as Continuum is a spin-off of Maven project it should be
    better
    integrated with it. But on the other hand, CruiseControl seems more mature
    to me, even if, to be honnest, I haven't tried any of them in a real
    situation yet. That's why I need something more concrete. Is there any
    Maven
    2 cruisecontrol plugin somewhere as there was one for Maven 1 ? What do
    you
    think ?

    --
    Sébastien Arbogast

    The Epseelon Project : http://www.epseelon.net
    Blog : http://sebastien-arbogast.epseelon.net
    TagSpot : http://www.tagspot.org
    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
    For additional commands, e-mail: users-help@maven.apache.org


    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
    For additional commands, e-mail: users-help@maven.apache.org
  • Sebastien Arbogast at May 4, 2006 at 9:25 am
    Honestly, intuitively I have a small preference for CruiseControl. The only
    thing that bothers me is the redundancy of information between the POM and
    CC configuration file. So if there was a Maven2 plugin to generate the
    latter from the former, as there was one for Maven1, that would be great.

    2006/5/4, Kieran Brady <kieran.brady@teamcgi.net>:
    We're using the latest CruiseControl with Maven 2 successfully - no
    problem
    configuring it. At the time I neeeded to implement a CI system back in
    October, Continuum wasn't mature enough and I couldn't realistically put
    it
    forward as an option as I couldn't get it to work :) I haven't tried
    Continuum since as CruiseControl has been happily doing multi-module
    builds,
    single projects, profiled builds, nightly builds running all reports, on
    demand builds and so on and so I've no reason to migrate.

    A couple of links:

    http://cruisecontrol.sourceforge.net/main/configxml.html
    http://jira.public.thoughtworks.org/browse/CC-363
    http://confluence.public.thoughtworks.org/display/CC/Home


    ----- Original Message -----
    From: "Alexandre Poitras" <alexandre.poitras@gmail.com>
    To: "Maven Users List" <users@maven.apache.org>
    Sent: Thursday, May 04, 2006 3:52 AM
    Subject: Re: [m2] Continuum or CruiseControl as a CI server ?


    Well Continuum does the job for me, never thought about switching.
    What I like about continuum is that you can customize the goals
    invoked during a build (for instance, clean site:deploy deploy). I
    have never used cruise control but I heard it's hard to configure.
    On 5/3/06, Sebastien Arbogast wrote:
    I'm trying to find the best CI tool for a brand new Maven2-built project
    and
    I'd like to have your experience feedback about which one to choose
    between
    Continuum and CruiseControl.
    I know that, as Continuum is a spin-off of Maven project it should be
    better
    integrated with it. But on the other hand, CruiseControl seems more mature
    to me, even if, to be honnest, I haven't tried any of them in a real
    situation yet. That's why I need something more concrete. Is there any
    Maven
    2 cruisecontrol plugin somewhere as there was one for Maven 1 ? What do
    you
    think ?

    --
    Sébastien Arbogast

    The Epseelon Project : http://www.epseelon.net
    Blog : http://sebastien-arbogast.epseelon.net
    TagSpot : http://www.tagspot.org
    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
    For additional commands, e-mail: users-help@maven.apache.org


    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
    For additional commands, e-mail: users-help@maven.apache.org

    --
    Sébastien Arbogast

    The Epseelon Project : http://www.epseelon.net
    Blog : http://sebastien-arbogast.epseelon.net
    TagSpot : http://www.tagspot.org
  • Kaare Nilsen at May 4, 2006 at 9:38 am
    There is one(cruisecontrol config generation) started at the mojo project.
    http://svn.mojo.codehaus.org/trunk/mojo/mojo-sandbox/cruisecontrol-maven-plugin/

    You can download this and install it manually and give it a go (though
    very early in the dev process, and only supports subversion and mail
    notifs), it will generate a cruisecontrol setup which will act the
    same way as an add m2 project in continuum.
    Also a mvn site:site on it will provide you with some documentation on use.

    /Kaare
    On 04/05/06, Sebastien Arbogast wrote:
    Honestly, intuitively I have a small preference for CruiseControl. The only
    thing that bothers me is the redundancy of information between the POM and
    CC configuration file. So if there was a Maven2 plugin to generate the
    latter from the former, as there was one for Maven1, that would be great.

    2006/5/4, Kieran Brady <kieran.brady@teamcgi.net>:
    We're using the latest CruiseControl with Maven 2 successfully - no
    problem
    configuring it. At the time I neeeded to implement a CI system back in
    October, Continuum wasn't mature enough and I couldn't realistically put
    it
    forward as an option as I couldn't get it to work :) I haven't tried
    Continuum since as CruiseControl has been happily doing multi-module
    builds,
    single projects, profiled builds, nightly builds running all reports, on
    demand builds and so on and so I've no reason to migrate.

    A couple of links:

    http://cruisecontrol.sourceforge.net/main/configxml.html
    http://jira.public.thoughtworks.org/browse/CC-363
    http://confluence.public.thoughtworks.org/display/CC/Home


    ----- Original Message -----
    From: "Alexandre Poitras" <alexandre.poitras@gmail.com>
    To: "Maven Users List" <users@maven.apache.org>
    Sent: Thursday, May 04, 2006 3:52 AM
    Subject: Re: [m2] Continuum or CruiseControl as a CI server ?


    Well Continuum does the job for me, never thought about switching.
    What I like about continuum is that you can customize the goals
    invoked during a build (for instance, clean site:deploy deploy). I
    have never used cruise control but I heard it's hard to configure.
    On 5/3/06, Sebastien Arbogast wrote:
    I'm trying to find the best CI tool for a brand new Maven2-built project
    and
    I'd like to have your experience feedback about which one to choose
    between
    Continuum and CruiseControl.
    I know that, as Continuum is a spin-off of Maven project it should be
    better
    integrated with it. But on the other hand, CruiseControl seems more mature
    to me, even if, to be honnest, I haven't tried any of them in a real
    situation yet. That's why I need something more concrete. Is there any
    Maven
    2 cruisecontrol plugin somewhere as there was one for Maven 1 ? What do
    you
    think ?

    --
    Sébastien Arbogast

    The Epseelon Project : http://www.epseelon.net
    Blog : http://sebastien-arbogast.epseelon.net
    TagSpot : http://www.tagspot.org
    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
    For additional commands, e-mail: users-help@maven.apache.org


    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
    For additional commands, e-mail: users-help@maven.apache.org

    --
    Sébastien Arbogast

    The Epseelon Project : http://www.epseelon.net
    Blog : http://sebastien-arbogast.epseelon.net
    TagSpot : http://www.tagspot.org
    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
    For additional commands, e-mail: users-help@maven.apache.org
  • Sebastien Arbogast at May 4, 2006 at 9:43 am
    It's fine for Subversion and mail notifications. But are these the only
    limitations of this development version ? In particular, is it safe to use
    it on a multi-module project ?


    2006/5/4, Kaare Nilsen <kaare.nilsen@gmail.com>:
    There is one(cruisecontrol config generation) started at the mojo project.

    http://svn.mojo.codehaus.org/trunk/mojo/mojo-sandbox/cruisecontrol-maven-plugin/

    You can download this and install it manually and give it a go (though
    very early in the dev process, and only supports subversion and mail
    notifs), it will generate a cruisecontrol setup which will act the
    same way as an add m2 project in continuum.
    Also a mvn site:site on it will provide you with some documentation on
    use.

    /Kaare
    On 04/05/06, Sebastien Arbogast wrote:
    Honestly, intuitively I have a small preference for CruiseControl. The only
    thing that bothers me is the redundancy of information between the POM and
    CC configuration file. So if there was a Maven2 plugin to generate the
    latter from the former, as there was one for Maven1, that would be great.
    2006/5/4, Kieran Brady <kieran.brady@teamcgi.net>:
    We're using the latest CruiseControl with Maven 2 successfully - no
    problem
    configuring it. At the time I neeeded to implement a CI system back in
    October, Continuum wasn't mature enough and I couldn't realistically
    put
    it
    forward as an option as I couldn't get it to work :) I haven't tried
    Continuum since as CruiseControl has been happily doing multi-module
    builds,
    single projects, profiled builds, nightly builds running all reports,
    on
    demand builds and so on and so I've no reason to migrate.

    A couple of links:

    http://cruisecontrol.sourceforge.net/main/configxml.html
    http://jira.public.thoughtworks.org/browse/CC-363
    http://confluence.public.thoughtworks.org/display/CC/Home


    ----- Original Message -----
    From: "Alexandre Poitras" <alexandre.poitras@gmail.com>
    To: "Maven Users List" <users@maven.apache.org>
    Sent: Thursday, May 04, 2006 3:52 AM
    Subject: Re: [m2] Continuum or CruiseControl as a CI server ?


    Well Continuum does the job for me, never thought about switching.
    What I like about continuum is that you can customize the goals
    invoked during a build (for instance, clean site:deploy deploy). I
    have never used cruise control but I heard it's hard to configure.
    On 5/3/06, Sebastien Arbogast wrote:
    I'm trying to find the best CI tool for a brand new Maven2-built
    project
    and
    I'd like to have your experience feedback about which one to choose
    between
    Continuum and CruiseControl.
    I know that, as Continuum is a spin-off of Maven project it should
    be
    better
    integrated with it. But on the other hand, CruiseControl seems more mature
    to me, even if, to be honnest, I haven't tried any of them in a real
    situation yet. That's why I need something more concrete. Is there
    any
    Maven
    2 cruisecontrol plugin somewhere as there was one for Maven 1 ? What
    do
    you
    think ?

    --
    Sébastien Arbogast

    The Epseelon Project : http://www.epseelon.net
    Blog : http://sebastien-arbogast.epseelon.net
    TagSpot : http://www.tagspot.org
    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
    For additional commands, e-mail: users-help@maven.apache.org


    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
    For additional commands, e-mail: users-help@maven.apache.org

    --
    Sébastien Arbogast

    The Epseelon Project : http://www.epseelon.net
    Blog : http://sebastien-arbogast.epseelon.net
    TagSpot : http://www.tagspot.org
    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
    For additional commands, e-mail: users-help@maven.apache.org

    --
    Sébastien Arbogast

    The Epseelon Project : http://www.epseelon.net
    Blog : http://sebastien-arbogast.epseelon.net
    TagSpot : http://www.tagspot.org
  • Kaare Nilsen at May 4, 2006 at 9:55 am
    Well.. i use it myself :)
    But yes there are several limitations in multi-module projects and
    cruise control in general. As of now we do not have any clever
    solutions for making sure that when one module changes, then the
    modules that depends on it also get build, the reactor build order is
    not considered and so on, but we are in the process of working out
    some of the issues, but it will for sure take a while before
    cruisecontrol can be as good as continuum when it comes to maven2
    support (most likly never).

    /K
    On 04/05/06, Sebastien Arbogast wrote:
    It's fine for Subversion and mail notifications. But are these the only
    limitations of this development version ? In particular, is it safe to use
    it on a multi-module project ?


    2006/5/4, Kaare Nilsen <kaare.nilsen@gmail.com>:
    There is one(cruisecontrol config generation) started at the mojo project.

    http://svn.mojo.codehaus.org/trunk/mojo/mojo-sandbox/cruisecontrol-maven-plugin/

    You can download this and install it manually and give it a go (though
    very early in the dev process, and only supports subversion and mail
    notifs), it will generate a cruisecontrol setup which will act the
    same way as an add m2 project in continuum.
    Also a mvn site:site on it will provide you with some documentation on
    use.

    /Kaare
    On 04/05/06, Sebastien Arbogast wrote:
    Honestly, intuitively I have a small preference for CruiseControl. The only
    thing that bothers me is the redundancy of information between the POM and
    CC configuration file. So if there was a Maven2 plugin to generate the
    latter from the former, as there was one for Maven1, that would be great.
    2006/5/4, Kieran Brady <kieran.brady@teamcgi.net>:
    We're using the latest CruiseControl with Maven 2 successfully - no
    problem
    configuring it. At the time I neeeded to implement a CI system back in
    October, Continuum wasn't mature enough and I couldn't realistically
    put
    it
    forward as an option as I couldn't get it to work :) I haven't tried
    Continuum since as CruiseControl has been happily doing multi-module
    builds,
    single projects, profiled builds, nightly builds running all reports,
    on
    demand builds and so on and so I've no reason to migrate.

    A couple of links:

    http://cruisecontrol.sourceforge.net/main/configxml.html
    http://jira.public.thoughtworks.org/browse/CC-363
    http://confluence.public.thoughtworks.org/display/CC/Home


    ----- Original Message -----
    From: "Alexandre Poitras" <alexandre.poitras@gmail.com>
    To: "Maven Users List" <users@maven.apache.org>
    Sent: Thursday, May 04, 2006 3:52 AM
    Subject: Re: [m2] Continuum or CruiseControl as a CI server ?


    Well Continuum does the job for me, never thought about switching.
    What I like about continuum is that you can customize the goals
    invoked during a build (for instance, clean site:deploy deploy). I
    have never used cruise control but I heard it's hard to configure.
    On 5/3/06, Sebastien Arbogast wrote:
    I'm trying to find the best CI tool for a brand new Maven2-built
    project
    and
    I'd like to have your experience feedback about which one to choose
    between
    Continuum and CruiseControl.
    I know that, as Continuum is a spin-off of Maven project it should
    be
    better
    integrated with it. But on the other hand, CruiseControl seems more mature
    to me, even if, to be honnest, I haven't tried any of them in a real
    situation yet. That's why I need something more concrete. Is there
    any
    Maven
    2 cruisecontrol plugin somewhere as there was one for Maven 1 ? What
    do
    you
    think ?

    --
    Sébastien Arbogast

    The Epseelon Project : http://www.epseelon.net
    Blog : http://sebastien-arbogast.epseelon.net
    TagSpot : http://www.tagspot.org
    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
    For additional commands, e-mail: users-help@maven.apache.org


    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
    For additional commands, e-mail: users-help@maven.apache.org

    --
    Sébastien Arbogast

    The Epseelon Project : http://www.epseelon.net
    Blog : http://sebastien-arbogast.epseelon.net
    TagSpot : http://www.tagspot.org
    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
    For additional commands, e-mail: users-help@maven.apache.org

    --
    Sébastien Arbogast

    The Epseelon Project : http://www.epseelon.net
    Blog : http://sebastien-arbogast.epseelon.net
    TagSpot : http://www.tagspot.org
    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
    For additional commands, e-mail: users-help@maven.apache.org
  • Jerome lacoste at May 4, 2006 at 10:37 am

    On 5/4/06, Kaare Nilsen wrote:
    Well.. i use it myself :)
    But yes there are several limitations in multi-module projects and
    cruise control in general. As of now we do not have any clever
    solutions for making sure that when one module changes, then the
    modules that depends on it also get build, the reactor build order is
    not considered and so on, but we are in the process of working out
    some of the issues, but it will for sure take a while before
    cruisecontrol can be as good as continuum when it comes to maven2
    support (most likly never).
    Sebastien,

    you may want to have a look:

    http://www.coffeebreaks.org/blogs/?page_id=15

    In the last slides of the CC & m2 talk, there's some information on
    how to minimize the information in the pom.

    As to the main issues to solve (information redundancy and build
    order), there's the mojo plugin Kaare pointed you to that we are going
    to improve. The main question today when using CC is to decide the
    granularity you want to have (do you map every pom to a project or
    not?), because CC relies today on m2's reactor to identify the correct
    build order, thus requires you to have a somewhat coarse grained
    mapping.

    I am pretty certain CC's support for m2 will improve a lot in the next
    months, althought I think today's it is pretty good. I use it to build
    without problems several OSS projects whose build is based on m2 as
    well as some closed source software. One of the CC install has around
    200 maven sub-projects, grouped into a handfull of CC projects. That
    works because the projects themselves are pretty fast to build.

    Jerome

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
    For additional commands, e-mail: users-help@maven.apache.org
  • Eric Pugh at May 4, 2006 at 11:41 am
    I used to be a big advocate of CC. I've had a contribution committed
    to the main code base in almost everyone of the last couple point
    releases. My big beef with CC breaks down to two things:

    1) Speed
    2) Web interface

    I find that with long builds that output a lot of data, the CC method
    of using XSL transformations to pull data out is too painful. It
    works, but it's slow. I also dislike the lack of a web interface for
    managing the application. Sure, there is a JMX interface, but it is
    clunky to use. And I can't add/remove builds from the web
    interface. I have to log onto my remote build server and tweak
    another xml file.

    In contrast, Continuum is all web configurable. It's fast because it
    doesn't parse the log file, it just looks for the result of the
    build. Unless you need some of the advanced stuff the CC provides,
    like some of the notifiers or SCM support, Continuum just works better.

    Eric

    On May 4, 2006, at 11:36 AM, jerome lacoste wrote:
    On 5/4/06, Kaare Nilsen wrote:
    Well.. i use it myself :)
    But yes there are several limitations in multi-module projects and
    cruise control in general. As of now we do not have any clever
    solutions for making sure that when one module changes, then the
    modules that depends on it also get build, the reactor build order is
    not considered and so on, but we are in the process of working out
    some of the issues, but it will for sure take a while before
    cruisecontrol can be as good as continuum when it comes to maven2
    support (most likly never).
    Sebastien,

    you may want to have a look:

    http://www.coffeebreaks.org/blogs/?page_id=15

    In the last slides of the CC & m2 talk, there's some information on
    how to minimize the information in the pom.

    As to the main issues to solve (information redundancy and build
    order), there's the mojo plugin Kaare pointed you to that we are going
    to improve. The main question today when using CC is to decide the
    granularity you want to have (do you map every pom to a project or
    not?), because CC relies today on m2's reactor to identify the correct
    build order, thus requires you to have a somewhat coarse grained
    mapping.

    I am pretty certain CC's support for m2 will improve a lot in the next
    months, althought I think today's it is pretty good. I use it to build
    without problems several OSS projects whose build is based on m2 as
    well as some closed source software. One of the CC install has around
    200 maven sub-projects, grouped into a handfull of CC projects. That
    works because the projects themselves are pretty fast to build.

    Jerome

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
    For additional commands, e-mail: users-help@maven.apache.org

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
    For additional commands, e-mail: users-help@maven.apache.org
  • Jerome lacoste at May 4, 2006 at 11:51 am

    On 5/4/06, Eric Pugh wrote:
    I used to be a big advocate of CC. I've had a contribution committed
    to the main code base in almost everyone of the last couple point
    releases. My big beef with CC breaks down to two things:

    1) Speed
    2) Web interface

    I find that with long builds that output a lot of data, the CC method
    of using XSL transformations to pull data out is too painful.
    It works, but it's slow.
    I generally agree though:

    - XSL transformations are cached. so the transformation cost happens once.
    - we could always change the webapp to preformat the pages before one
    gets to see the pages.
    - you can also configure the app to minimize the information to store
    in the logs and keep the raw logs on the side.
    I also dislike the lack of a web interface for
    managing the application. Sure, there is a JMX interface, but it is
    clunky to use. And I can't add/remove builds from the web
    interface. I have to log onto my remote build server and tweak
    another xml file.
    1- there's a web interface in the works
    2- you can use the ccconfig project to remotely edit the config file

    The thing that bothers me most with CC is that you have to make the
    initial checkout by hand.
    In contrast, Continuum is all web configurable. It's fast because it
    doesn't parse the log file, it just looks for the result of the
    build. Unless you need some of the advanced stuff the CC provides,
    like some of the notifiers or SCM support, Continuum just works better.
    I guess that in the future, CC will become easier to use and Continuum
    will have more high end features.

    J

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
    For additional commands, e-mail: users-help@maven.apache.org
  • Sebastien Arbogast at May 4, 2006 at 9:59 am
    I've checked it out, and when I tried to run mvn install on it, I got the
    following exception:

    W:\data\dev\cruisecontrol-maven-plugin>mvn install
    [INFO] Scanning for projects...
    [INFO]
    ------------------------------------------------------------------------
    [ERROR] FATAL ERROR
    [INFO]
    ------------------------------------------------------------------------
    [INFO] Failed to resolve artifact.

    GroupId: org.codehaus.mojo
    ArtifactId: mojo-sandbox
    Version: 2-SNAPSHOT

    Reason: Unable to download the artifact from any repository

    org.codehaus.mojo:mojo-sandbox:pom:2-SNAPSHOT

    from the specified remote repositories:
    central (http://repo1.maven.org/maven2)


    [INFO]
    ------------------------------------------------------------------------
    [INFO] Trace
    org.apache.maven.reactor.MavenExecutionException: Cannot find parent:
    org.codeha
    us.mojo:mojo-sandbox for project:
    null:cruisecontrol-maven-plugin:maven-plugin:1
    .0-SNAPSHOT
    at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:365)
    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:278)
    at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
    at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke
    (NativeMethodAccessorImpl.
    java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke
    (DelegatingMethodAcces
    sorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java
    :315)
    at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
    at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java
    :430)

    at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
    Caused by: org.apache.maven.project.ProjectBuildingException: Cannot find
    parent
    : org.codehaus.mojo:mojo-sandbox for project:
    null:cruisecontrol-maven-plugin:ma
    ven-plugin:1.0-SNAPSHOT
    at
    org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(D
    efaultMavenProjectBuilder.java:1161)
    at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal
    (Def
    aultMavenProjectBuilder.java:674)
    at
    org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFi
    leInternal(DefaultMavenProjectBuilder.java:416)
    at org.apache.maven.project.DefaultMavenProjectBuilder.build
    (DefaultMave
    nProjectBuilder.java:192)
    at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:515)
    at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java
    :447)
    at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:351)
    ... 11 more
    Caused by: org.apache.maven.project.ProjectBuildingException: POM '
    org.codehaus.
    mojo:mojo-sandbox' not found in repository: Unable to download the artifact
    from
    any repository

    org.codehaus.mojo:mojo-sandbox:pom:2-SNAPSHOT

    from the specified remote repositories:
    central (http://repo1.maven.org/maven2)

    at
    org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepo
    sitory(DefaultMavenProjectBuilder.java:513)
    at
    org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(D
    efaultMavenProjectBuilder.java:1157)
    ... 17 more
    Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException:
    Unable
    to download the artifact from any repository

    org.codehaus.mojo:mojo-sandbox:pom:2-SNAPSHOT

    from the specified remote repositories:
    central (http://repo1.maven.org/maven2)

    at
    org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(De
    faultArtifactResolver.java:136)
    at
    org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(De
    faultArtifactResolver.java:63)
    at
    org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepo
    sitory(DefaultMavenProjectBuilder.java:467)
    ... 18 more
    Caused by: org.apache.maven.wagon.ResourceDoesNotExistException: Unable to
    downl
    oad the artifact from any repository
    at org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact
    (Def
    aultWagonManager.java:260)
    at
    org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(De
    faultArtifactResolver.java:124)
    ... 20 more
    [INFO]
    ------------------------------------------------------------------------
    [INFO] Total time: < 1 second
    [INFO] Finished at: Thu May 04 11:55:23 CEST 2006
    [INFO] Final Memory: 1M/2M
    [INFO]
    ------------------------------------------------------------------------

    I guess I must configure codehaus repository somewhere but I don't know how.

    2006/5/4, Sebastien Arbogast <sebastien.arbogast@gmail.com>:
    It's fine for Subversion and mail notifications. But are these the only
    limitations of this development version ? In particular, is it safe to use
    it on a multi-module project ?


    2006/5/4, Kaare Nilsen < kaare.nilsen@gmail.com>:
    There is one(cruisecontrol config generation) started at the mojo
    project.

    http://svn.mojo.codehaus.org/trunk/mojo/mojo-sandbox/cruisecontrol-maven-plugin/

    You can download this and install it manually and give it a go (though
    very early in the dev process, and only supports subversion and mail
    notifs), it will generate a cruisecontrol setup which will act the
    same way as an add m2 project in continuum.
    Also a mvn site:site on it will provide you with some documentation on
    use.

    /Kaare
    On 04/05/06, Sebastien Arbogast wrote:
    Honestly, intuitively I have a small preference for CruiseControl. The only
    thing that bothers me is the redundancy of information between the POM and
    CC configuration file. So if there was a Maven2 plugin to generate the
    latter from the former, as there was one for Maven1, that would be great.
    2006/5/4, Kieran Brady <kieran.brady@teamcgi.net>:
    We're using the latest CruiseControl with Maven 2 successfully - no
    problem
    configuring it. At the time I neeeded to implement a CI system back
    in
    October, Continuum wasn't mature enough and I couldn't realistically
    put
    it
    forward as an option as I couldn't get it to work :) I haven't tried
    Continuum since as CruiseControl has been happily doing multi-module
    builds,
    single projects, profiled builds, nightly builds running all
    reports, on
    demand builds and so on and so I've no reason to migrate.

    A couple of links:

    http://cruisecontrol.sourceforge.net/main/configxml.html
    http://jira.public.thoughtworks.org/browse/CC-363
    http://confluence.public.thoughtworks.org/display/CC/Home


    ----- Original Message -----
    From: "Alexandre Poitras" <alexandre.poitras@gmail.com>
    To: "Maven Users List" < users@maven.apache.org>
    Sent: Thursday, May 04, 2006 3:52 AM
    Subject: Re: [m2] Continuum or CruiseControl as a CI server ?


    Well Continuum does the job for me, never thought about switching.
    What I like about continuum is that you can customize the goals
    invoked during a build (for instance, clean site:deploy deploy). I
    have never used cruise control but I heard it's hard to configure.
    On 5/3/06, Sebastien Arbogast wrote:
    I'm trying to find the best CI tool for a brand new Maven2-built
    project
    and
    I'd like to have your experience feedback about which one to
    choose
    between
    Continuum and CruiseControl.
    I know that, as Continuum is a spin-off of Maven project it should
    be
    better
    integrated with it. But on the other hand, CruiseControl seems
    more
    mature
    to me, even if, to be honnest, I haven't tried any of them in a
    real
    situation yet. That's why I need something more concrete. Is there
    any
    Maven
    2 cruisecontrol plugin somewhere as there was one for Maven 1 ?
    What do
    you
    think ?

    --
    Sébastien Arbogast

    The Epseelon Project : http://www.epseelon.net
    Blog : http://sebastien-arbogast.epseelon.net
    TagSpot : http://www.tagspot.org
    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
    For additional commands, e-mail: users-help@maven.apache.org

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
    For additional commands, e-mail: users-help@maven.apache.org

    --
    Sébastien Arbogast

    The Epseelon Project : http://www.epseelon.net
    Blog : http://sebastien-arbogast.epseelon.net
    TagSpot : http://www.tagspot.org
    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
    For additional commands, e-mail: users-help@maven.apache.org

    --

    Sébastien Arbogast

    The Epseelon Project : http://www.epseelon.net
    Blog : http://sebastien-arbogast.epseelon.net
    TagSpot : http://www.tagspot.org


    --
    Sébastien Arbogast

    The Epseelon Project : http://www.epseelon.net
    Blog : http://sebastien-arbogast.epseelon.net
    TagSpot : http://www.tagspot.org
  • Kaare Nilsen at May 4, 2006 at 10:04 am
    Sorry about that.. I have everything setup on my machine, so I forgot
    to point out that there is something more to be done, when building
    plugins in the sanbox :)

    But you will need to add the repositories as documented here:
    http://mojo.codehaus.org/using-sandbox-plugins.html to your checked
    out version of the pom, and then it should build quite ok

    /Kaare
    On 04/05/06, Sebastien Arbogast wrote:
    I've checked it out, and when I tried to run mvn install on it, I got the
    following exception:

    W:\data\dev\cruisecontrol-maven-plugin>mvn install
    [INFO] Scanning for projects...
    [INFO]
    ------------------------------------------------------------------------
    [ERROR] FATAL ERROR
    [INFO]
    ------------------------------------------------------------------------
    [INFO] Failed to resolve artifact.

    GroupId: org.codehaus.mojo
    ArtifactId: mojo-sandbox
    Version: 2-SNAPSHOT

    Reason: Unable to download the artifact from any repository

    org.codehaus.mojo:mojo-sandbox:pom:2-SNAPSHOT

    from the specified remote repositories:
    central (http://repo1.maven.org/maven2)


    [INFO]
    ------------------------------------------------------------------------
    [INFO] Trace
    org.apache.maven.reactor.MavenExecutionException: Cannot find parent:
    org.codeha
    us.mojo:mojo-sandbox for project:
    null:cruisecontrol-maven-plugin:maven-plugin:1
    .0-SNAPSHOT
    at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:365)
    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:278)
    at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
    at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke
    (NativeMethodAccessorImpl.
    java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke
    (DelegatingMethodAcces
    sorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java
    :315)
    at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
    at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java
    :430)

    at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
    Caused by: org.apache.maven.project.ProjectBuildingException: Cannot find
    parent
    : org.codehaus.mojo:mojo-sandbox for project:
    null:cruisecontrol-maven-plugin:ma
    ven-plugin:1.0-SNAPSHOT
    at
    org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(D
    efaultMavenProjectBuilder.java:1161)
    at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal
    (Def
    aultMavenProjectBuilder.java:674)
    at
    org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFi
    leInternal(DefaultMavenProjectBuilder.java:416)
    at org.apache.maven.project.DefaultMavenProjectBuilder.build
    (DefaultMave
    nProjectBuilder.java:192)
    at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:515)
    at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java
    :447)
    at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:351)
    ... 11 more
    Caused by: org.apache.maven.project.ProjectBuildingException: POM '
    org.codehaus.
    mojo:mojo-sandbox' not found in repository: Unable to download the artifact
    from
    any repository

    org.codehaus.mojo:mojo-sandbox:pom:2-SNAPSHOT

    from the specified remote repositories:
    central (http://repo1.maven.org/maven2)

    at
    org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepo
    sitory(DefaultMavenProjectBuilder.java:513)
    at
    org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(D
    efaultMavenProjectBuilder.java:1157)
    ... 17 more
    Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException:
    Unable
    to download the artifact from any repository

    org.codehaus.mojo:mojo-sandbox:pom:2-SNAPSHOT

    from the specified remote repositories:
    central (http://repo1.maven.org/maven2)

    at
    org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(De
    faultArtifactResolver.java:136)
    at
    org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(De
    faultArtifactResolver.java:63)
    at
    org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepo
    sitory(DefaultMavenProjectBuilder.java:467)
    ... 18 more
    Caused by: org.apache.maven.wagon.ResourceDoesNotExistException: Unable to
    downl
    oad the artifact from any repository
    at org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact
    (Def
    aultWagonManager.java:260)
    at
    org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(De
    faultArtifactResolver.java:124)
    ... 20 more
    [INFO]
    ------------------------------------------------------------------------
    [INFO] Total time: < 1 second
    [INFO] Finished at: Thu May 04 11:55:23 CEST 2006
    [INFO] Final Memory: 1M/2M
    [INFO]
    ------------------------------------------------------------------------

    I guess I must configure codehaus repository somewhere but I don't know how.

    2006/5/4, Sebastien Arbogast <sebastien.arbogast@gmail.com>:
    It's fine for Subversion and mail notifications. But are these the only
    limitations of this development version ? In particular, is it safe to use
    it on a multi-module project ?


    2006/5/4, Kaare Nilsen < kaare.nilsen@gmail.com>:
    There is one(cruisecontrol config generation) started at the mojo
    project.

    http://svn.mojo.codehaus.org/trunk/mojo/mojo-sandbox/cruisecontrol-maven-plugin/

    You can download this and install it manually and give it a go (though
    very early in the dev process, and only supports subversion and mail
    notifs), it will generate a cruisecontrol setup which will act the
    same way as an add m2 project in continuum.
    Also a mvn site:site on it will provide you with some documentation on
    use.

    /Kaare
    On 04/05/06, Sebastien Arbogast wrote:
    Honestly, intuitively I have a small preference for CruiseControl. The only
    thing that bothers me is the redundancy of information between the POM and
    CC configuration file. So if there was a Maven2 plugin to generate the
    latter from the former, as there was one for Maven1, that would be great.
    2006/5/4, Kieran Brady <kieran.brady@teamcgi.net>:
    We're using the latest CruiseControl with Maven 2 successfully - no
    problem
    configuring it. At the time I neeeded to implement a CI system back
    in
    October, Continuum wasn't mature enough and I couldn't realistically
    put
    it
    forward as an option as I couldn't get it to work :) I haven't tried
    Continuum since as CruiseControl has been happily doing multi-module
    builds,
    single projects, profiled builds, nightly builds running all
    reports, on
    demand builds and so on and so I've no reason to migrate.

    A couple of links:

    http://cruisecontrol.sourceforge.net/main/configxml.html
    http://jira.public.thoughtworks.org/browse/CC-363
    http://confluence.public.thoughtworks.org/display/CC/Home


    ----- Original Message -----
    From: "Alexandre Poitras" <alexandre.poitras@gmail.com>
    To: "Maven Users List" < users@maven.apache.org>
    Sent: Thursday, May 04, 2006 3:52 AM
    Subject: Re: [m2] Continuum or CruiseControl as a CI server ?


    Well Continuum does the job for me, never thought about switching.
    What I like about continuum is that you can customize the goals
    invoked during a build (for instance, clean site:deploy deploy). I
    have never used cruise control but I heard it's hard to configure.
    On 5/3/06, Sebastien Arbogast wrote:
    I'm trying to find the best CI tool for a brand new Maven2-built
    project
    and
    I'd like to have your experience feedback about which one to
    choose
    between
    Continuum and CruiseControl.
    I know that, as Continuum is a spin-off of Maven project it should
    be
    better
    integrated with it. But on the other hand, CruiseControl seems
    more
    mature
    to me, even if, to be honnest, I haven't tried any of them in a
    real
    situation yet. That's why I need something more concrete. Is there
    any
    Maven
    2 cruisecontrol plugin somewhere as there was one for Maven 1 ?
    What do
    you
    think ?

    --
    Sébastien Arbogast

    The Epseelon Project : http://www.epseelon.net
    Blog : http://sebastien-arbogast.epseelon.net
    TagSpot : http://www.tagspot.org
    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
    For additional commands, e-mail: users-help@maven.apache.org

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
    For additional commands, e-mail: users-help@maven.apache.org

    --
    Sébastien Arbogast

    The Epseelon Project : http://www.epseelon.net
    Blog : http://sebastien-arbogast.epseelon.net
    TagSpot : http://www.tagspot.org
    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
    For additional commands, e-mail: users-help@maven.apache.org

    --

    Sébastien Arbogast

    The Epseelon Project : http://www.epseelon.net
    Blog : http://sebastien-arbogast.epseelon.net
    TagSpot : http://www.tagspot.org


    --
    Sébastien Arbogast

    The Epseelon Project : http://www.epseelon.net
    Blog : http://sebastien-arbogast.epseelon.net
    TagSpot : http://www.tagspot.org
    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
    For additional commands, e-mail: users-help@maven.apache.org
  • Geoffrey De Smet at May 4, 2006 at 11:51 am
    I 've used both continuum and cruisecontrol, IMHO continuum is a lot
    better and easier, especially for maven 2 multiprojects.

    Sebastien Arbogast wrote:
    I'm trying to find the best CI tool for a brand new Maven2-built project
    and
    I'd like to have your experience feedback about which one to choose between
    Continuum and CruiseControl.
    I know that, as Continuum is a spin-off of Maven project it should be
    better
    integrated with it. But on the other hand, CruiseControl seems more mature
    to me, even if, to be honnest, I haven't tried any of them in a real
    situation yet. That's why I need something more concrete. Is there any
    Maven
    2 cruisecontrol plugin somewhere as there was one for Maven 1 ? What do you
    think ?

    --
    Sébastien Arbogast

    The Epseelon Project : http://www.epseelon.net
    Blog : http://sebastien-arbogast.epseelon.net
    TagSpot : http://www.tagspot.org
    --
    With kind regards,
    Geoffrey De Smet


    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
    For additional commands, e-mail: users-help@maven.apache.org
  • Siegmann Daniel, NY at May 4, 2006 at 12:57 pm
    We have been using CruiseControl for awhile now, with a number of projects
    running on M1. We are happy with it - happy enough that we will not be
    evaluating Continuum. When we switch to M2 (we're working on converting an
    ant project) we will continue using CC. The latest version of CC supports
    M2.

    --
    Daniel Siegmann
    FJA-US, Inc.
    (212) 840-2618 ext. 139
    -----Original Message-----
    From: Sebastien Arbogast
    Sent: Wednesday, May 03, 2006 7:28 PM
    To: Maven users list
    Subject: [m2] Continuum or CruiseControl as a CI server ?


    I'm trying to find the best CI tool for a brand new
    Maven2-built project and I'd like to have your experience
    feedback about which one to choose between Continuum and
    CruiseControl. I know that, as Continuum is a spin-off of
    Maven project it should be better integrated with it. But on
    the other hand, CruiseControl seems more mature to me, even
    if, to be honnest, I haven't tried any of them in a real
    situation yet. That's why I need something more concrete. Is
    there any Maven 2 cruisecontrol plugin somewhere as there was
    one for Maven 1 ? What do you think ?

    --
    Sébastien Arbogast

    The Epseelon Project : http://www.epseelon.net
    Blog : http://sebastien-arbogast.epseelon.net
    TagSpot : http://www.tagspot.org
    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
    For additional commands, e-mail: users-help@maven.apache.org
  • Siegmann Daniel, NY at May 4, 2006 at 1:01 pm

    clean site:deploy deploy). I have never used cruise control
    but I heard it's hard to configure.
    I have not found CruiseControl difficult to configure. It's not more
    difficult than Maven is, and adding more projects to the configuration is
    mostly copy-paste. CC also comes with a nice web-based status page (in
    addition to email reports) which is very simple to set up.

    --
    Daniel Siegmann
    FJA-US, Inc.
    (212) 840-2618 ext. 139

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
    For additional commands, e-mail: users-help@maven.apache.org
  • Eric Pugh at May 4, 2006 at 2:26 pm
    I think a lot of it just comes down to personal preference. If your
    decision isn't driven by a specific feature/missing feature of one or
    the other, then go with the one you are more comfortable with! Often
    having expertise in one or the other is a better reason to pick it.
    After all, it's just a glorified cron job! We should be spending
    time on coding, not CI.

    And, having multiple successful solutions is good for moving the
    market forward...

    Eric
    On May 4, 2006, at 2:00 PM, Siegmann Daniel, NY wrote:

    clean site:deploy deploy). I have never used cruise control
    but I heard it's hard to configure.
    I have not found CruiseControl difficult to configure. It's not more
    difficult than Maven is, and adding more projects to the
    configuration is
    mostly copy-paste. CC also comes with a nice web-based status page (in
    addition to email reports) which is very simple to set up.

    --
    Daniel Siegmann
    FJA-US, Inc.
    (212) 840-2618 ext. 139

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
    For additional commands, e-mail: users-help@maven.apache.org

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
    For additional commands, e-mail: users-help@maven.apache.org
  • Wayne Fay at May 4, 2006 at 2:29 pm
    Implement both, after 30 or 60 days, decide which one you like best
    and drop the other. ;-)

    Wayne
    On 5/4/06, Eric Pugh wrote:
    I think a lot of it just comes down to personal preference. If your
    decision isn't driven by a specific feature/missing feature of one or
    the other, then go with the one you are more comfortable with! Often
    having expertise in one or the other is a better reason to pick it.
    After all, it's just a glorified cron job! We should be spending
    time on coding, not CI.

    And, having multiple successful solutions is good for moving the
    market forward...

    Eric
    On May 4, 2006, at 2:00 PM, Siegmann Daniel, NY wrote:

    clean site:deploy deploy). I have never used cruise control
    but I heard it's hard to configure.
    I have not found CruiseControl difficult to configure. It's not more
    difficult than Maven is, and adding more projects to the
    configuration is
    mostly copy-paste. CC also comes with a nice web-based status page (in
    addition to email reports) which is very simple to set up.

    --
    Daniel Siegmann
    FJA-US, Inc.
    (212) 840-2618 ext. 139

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
    For additional commands, e-mail: users-help@maven.apache.org

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
    For additional commands, e-mail: users-help@maven.apache.org
    ---------------------------------------------------------------------
    To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
    For additional commands, e-mail: users-help@maven.apache.org

Related Discussions