Complex projects with lots of external dependencies, particularly
dependencies on external snapshot versions of code.
Also, we run a nightly integration test against external systems (we
only run Unit tests on the normal non-forced build, or they'd take too
long), and changes in the underlying dat
This would be useful if you are reverse engineering the database and
there is a database change. No cvs change but a table got modified.
--
tom
Not yet, why?
Emmanuel
Morgovsky, Alexander (US - Glen Mills) a écrit :
Is it possible to have Continuum force build every n hours even if the
code in the source code repository hasn't changed?
This message (including any attachments) contains confidential information intended for a specifi
er 20, 2006 2:31 PM
To: continuum-users@maven.apache.org
Subject: Re: Forced builds
No changes in code == no reason to build, right? I don't see the
usefulness of this enhancement, personally... Unless of course some
PHB has laid down a "build all projects every 3 hrs" kind of mandate
, November 20, 2006 2:22 PM
To: continuum-users@maven.apache.org
Subject: Re: Forced builds
Not yet, why?
Emmanuel
Morgovsky, Alexander (US - Glen Mills) a écrit :
> Is it possible to have Continuum force build every n hours even if the
> code in the source code repository hasn
No changes in code == no reason to build, right? I don't see the
usefulness of this enhancement, personally... Unless of course some
PHB has laid down a "build all projects every 3 hrs" kind of mandate
in your organization.
Wayne
On 11/20/06, Emmanuel Venisse <[EMAIL PROTECTED]> wrote:
Not yet,
Thanks for the good news.
-Original Message-
From: Christian Edward Gruber [mailto:[EMAIL PROTECTED]
Sent: Monday, November 20, 2006 4:20 PM
To: continuum-users@maven.apache.org
Subject: Re: Forced builds
Complex projects with lots of external dependencies, particularly
dependencies on
