In 1.1-alpha-2, build definition are independant and even if we don't have
changes since latest update, the build will run if you have changes since
latest execution of the current build definition.
Emmanuel
Julien Stern a écrit :
On Tue, Jun 19, 2007 at 08:11:59PM +0200, Emmanuel Venisse wrote:
You should run them in separate build definitions.
But if I do that, the second one will never run because nothing
will have changed, no ?
And If I do a fresh build, I will loose the output from the
first run...
--
Julien
Emmanuel
Julien Stern a écrit :
Hi list,
I would like to run several Maven2 goals for one project under
Continuum.
The problem is that some of these goals should be run in --non-recursive
mode, while some others should be run as a reactor.
One example would be to generate the dependency-convergence for
a lot of modules and then deploy the site but only for the top-level
modules (it takes days otherwise and continuum runs out of memory
anyway).
So, what I would need is to be able to run, for instance
mvn project-info-reports:dependency-convergence
and then
mvn --non-recursive site:deploy
But of course, these should be run from the same place and the second
command should be triggered even if the first one succeeds :)
Is there any way to do this in the 1.1-alpha-2 version of continuum?
--
Julien
