Mailing-List: contact continuum-users-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: continuum-users@maven.apache.org
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: intelligently building snapshots with continuum
Date: Wed, 20 Sep 2006 13:33:44 -0700
Message-ID: 
 <3FB08D6A21B3EC4D8749EF6D9E6262786FF383@WDCCPMAIL01.markettools.com>
In-Reply-To: <53FA92A1-C144-40BC-BC52-FCFC659C2D7A@diroussel.xsmail.com>
Thread-Topic: intelligently building snapshots with continuum
thread-index: Acbc7WSVS5UjlNx3SBOi0LZkBC1k/gABFrWg
From: "Leonard Gestrin" <Leonard.Gestrin@markettools.com>
To: <continuum-users@maven.apache.org>

Yes, but effectively this would rebuild everything and post new
snapshots for every component; the problems with that are:
1. developers would constantly be getting new snapshots for components
that did not have to be rebuilt. Then, it's a matter of what's faster -
building everything locally or syncing snapshots everytime developer
builds.
2. repository will get filled with snapshots that have identical
contents and there is no easy way to understand why new version of
particular snapshot have been built. (is it because it's sources have
been changed, it's dependency have been changed or nothing has changed).


My goal is to provide a system where build machine or don't have to
rebuild everything everytime there is a change.=20

I can think of creating a custom script that runs on continuum machine
that can be launched by developer remotely that would deploy new
snapshot for given module and also build dependency tree and deploy all
necessary snapshots recursively. Maybe, somebody already did something
like that so I don't need to reinvent the wheel.
Thanks


-----Original Message-----
From: David Roussel [mailto:continuum@diroussel.xsmail.com]=20
Sent: Wednesday, September 20, 2006 12:46 PM
To: continuum-users@maven.apache.org
Subject: Re: intelligently building snapshots with continuum


On 20 Sep 2006, at 20:04, Leonard Gestrin wrote:

> 3. if continuum does not have the answer for the problem/questions =20
> to 2.
> can someone recommend the alternative solution/intergration server =20
> that
> would ensure that snapshots are being incrementally deployed only when
> and in the right dependency order? (if change has been done in util
> module there is no need to redeploy common snapshot but there is a =20
> need
> to redeploy webutil once util snapshot is ready)

I don't know about the rest, but if you just want your snapshots to =20
be current.  Then just build your super pom recursively, and =20
everything below it will be built.

It doesn't do all the incremental stuff, but it ensures that trunk =20
builds ok.

David