preGoal problems

[Colin Chalmers <co...@maxware.nl>]

Hi all,

I've got a wee problem with a preGoal which is being run twice. I'm using b7 and trying to check out src from VSS before compiling. If I run "maven site" the preGoal below is run twice. How can I do this more efficiently?

/c

<snip>
  <preGoal name="java:compile">
  
     <delete dir="${java.src.local}"/>     

     <vssget localPath="${java.src.local}"
      recursive="true"
      login="${config.vss.uid},${config.vss.pwd}"
      serverPath="${vss.server.path}"
      vsspath="${vss.project}"
      writable="true">
     </vssget>
  </preGoal>
</snip>

Re: continuous integration

[Jean-François El Fouly <je...@wanadoo.fr>]

If I understand the question, I would answer that this functionality is 
provided through built-in support for gump.

A 12:44 12/02/2003 -0500, vous avez écrit :
>Hello,
>
>I was wondering if there is any facility built in or planned in Maven to 
>do continuous scheduled builds based on changes detected in a version 
>control system, as in cruise control / anthill?  Or is this beyond the 
>scope of maven?

Re: preGoal problems

[Colin Chalmers <co...@maxware.nl>]

Hi Colin,

Thanx for your comments. I've changed what was a preGoal to a goal in itself
(getSource), however now this has run everytime I run maven on this project.
Is it possible to change this so that it's only run in combination with
specific goals?

/c


----- Original Message -----
From: "Colin Sampaleanu" <co...@exis.com>
To: "Turbine Maven Users List" <tu...@jakarta.apache.org>
Sent: Wednesday, February 12, 2003 3:44 PM
Subject: Re: preGoal problems


> Colin Chalmers wrote:
>
> >Hi all,
> >
> >I've got a wee problem with a preGoal which is being run twice. I'm using
b7 and trying to check out src from VSS before compiling. If I run "maven
site" the preGoal below is run twice. How can I do this more efficiently?
> >
> >/c
> >
> ><snip>
> >  <preGoal name="java:compile">
> >
> >     <delete dir="${java.src.local}"/>
> >
> >     <vssget localPath="${java.src.local}"
> >      recursive="true"
> >      login="${config.vss.uid},${config.vss.pwd}"
> >      serverPath="${vss.server.path}"
> >      vsspath="${vss.project}"
> >      writable="true">
> >     </vssget>
> >  </preGoal>
> ></snip>
> >
> >
> You _may_ be being hit by the fact that goals in maven are somewhat
> broken right now, to the extent that attainGoal as used all over the
> place knows nothing goals which have been achieved. So if somewhere
> along your build chain there are two attainGoals for java:compile, it
> would be called twice. I've submitted code for werkz and maven which
> resolves this, but it's not it yet...
>
> As an aside, I would question uncoditionally doing a check out before
> every compile though, unless this project is never used interactively,
> e.g.only called as part of a nightly build or something like that. Even
> then, I would probably make it a separate goal which is called
separately...
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-maven-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail:
turbine-maven-user-help@jakarta.apache.org
>
>

continuous integration

[Sean Langford <me...@seanlangford.com>]

Hello,

I was wondering if there is any facility built in or planned in Maven to 
do continuous scheduled builds based on changes detected in a version 
control system, as in cruise control / anthill?  Or is this beyond the 
scope of maven?

thanks

Sean

Re: preGoal problems

[Colin Sampaleanu <co...@exis.com>]

Colin Chalmers wrote:

>Hi all,
>
>I've got a wee problem with a preGoal which is being run twice. I'm using b7 and trying to check out src from VSS before compiling. If I run "maven site" the preGoal below is run twice. How can I do this more efficiently?
>
>/c
>
><snip>
>  <preGoal name="java:compile">
>  
>     <delete dir="${java.src.local}"/>     
>
>     <vssget localPath="${java.src.local}"
>      recursive="true"
>      login="${config.vss.uid},${config.vss.pwd}"
>      serverPath="${vss.server.path}"
>      vsspath="${vss.project}"
>      writable="true">
>     </vssget>
>  </preGoal>
></snip>
>  
>
You _may_ be being hit by the fact that goals in maven are somewhat 
broken right now, to the extent that attainGoal as used all over the 
place knows nothing goals which have been achieved. So if somewhere 
along your build chain there are two attainGoals for java:compile, it 
would be called twice. I've submitted code for werkz and maven which 
resolves this, but it's not it yet...

As an aside, I would question uncoditionally doing a check out before 
every compile though, unless this project is never used interactively, 
e.g.only called as part of a nightly build or something like that. Even 
then, I would probably make it a separate goal which is called separately...