Re: Nightly Build Structure

[Dion Gillard <di...@gmail.com>]

We're happily using CC/Maven to build and deploy 20 odd WSAD projects to WAS 5.


On Thu, 30 Sep 2004 17:31:10 +0100, Colin Hawkett
<co...@morpheus.co.uk> wrote:
> Thanks Kim... just needed a vague pointer in the right direction -
> cheers,
> 
> Colin
> 
> 
> 
> -----Original Message-----
> From: Kim Goings [mailto:smilingjudy@mac.com]
> Sent: 30 September 2004 16:54
> To: Maven Users List
> Subject: Re: Nightly Build Structure
> 
> CruiseControl will do this for you.  Setup a CVS bootstrapper to grab
> the latest project.xml, etc. before running the build.
> 
> Kim
> 
> On Sep 30, 2004, at 5:39 AM, Colin Hawkett wrote:
> 
> > Hi,
> >
> >   I am trying to work out how best to use maven for the project
> > structures we have.  Basically we run a lot of large projects, using
> > WSAD as the development environment.  We do not want to use maven for
> > the development process.  There a number of reasons for this, but
> > generally it is because customers are often involved in the
> development
> > process, and the whole WSAD development/test run on server thing works
> > well for them.
> >
> >   What we do want to do is use maven for our nightly builds of all our
> > projects.  So we have everything in cvs in structure not identical to
> > the one recommended by maven, but we aren't in a position to modify
> > that
> > structure for the same reasons we will not be using maven to build
> > within our development environment.
> >
> >   So here we are with an empty build box and a server we want to
> deploy
> > all our projects to run all the test etc. and produce the project
> > website.  So we need the project.xml to run maven against -> which is
> 
> > in
> > CVS with each particular project -> which contains the information
> > about
> > connecting to CVS.... A bit of a chicken and the egg thing going on
> > here...
> >
> > It looks like we need a wrapper process around the whole thing to
> > control getting everything out of CVS and then running Maven against
> > all
> > of those project.xml files....
> >
> > First question - am I missing something really obvious here?
> >
> > Second question - assuming I'm not missing something really obvious,
> > whats do people recommend for this wrapper process?  Some things I
> have
> > considered are
> >
> > 1.  Plain old ANT (weren't we throwing that away?) checks out each
> > project, and runs maven against the project.xml we just checked out
> > 2.  Cruise Control?
> > 3.  Anthill?
> > 4.  Maven? Do we make the build of all these projects another maven
> > project?  From what I can see with what I have done in Maven - this
> > doesn't seem right, e.g. how to handle the fact that all these
> projects
> > are in different CVS repositories?
> >
> > At the moment option 1 seems the easiest - but I can't help feeling
> > that
> > I'm missing something here.
> >
> > Anyway - I'm sure this must be a problem people have come across and
> > found good ways of dealing with - any pointers would be welcome -
> > cheers,
> >
> > Colin
> >
> >
> >
> >
> >
> ***********************************************************************
> > *****
> >
> > This email and any files transmitted with it contain information that
> 
> > may be
> > confidential or privileged, and are intended solely for the use of the
> > individual or entity to whom they are addressed. If you are not the
> > intended
> > recipient any disclosure, copying, distribution or use of the
> > information is
> > prohibited. If you have received this email in error, please notify me
> 
> > by
> > return email immediately. Any opinions expressed are those of the
> > author,
> > not of Morpheus Limited.
> >
> >
> > This message has been checked for all known viruses by UUNET delivered
> > through the MessageLabs Virus Control Centre.
> >
> >
> ***********************************************************************
> > *****
> >
> > ---------------------------------------------------------------------
> > 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
> 
> 
> 
> 
> ****************************************************************************
> 
> This email and any files transmitted with it contain information that may be
> confidential or privileged, and are intended solely for the use of the
> individual or entity to whom they are addressed. If you are not the intended
> recipient any disclosure, copying, distribution or use of the information is
> prohibited. If you have received this email in error, please notify me by
> return email immediately. Any opinions expressed are those of the author,
> not of Morpheus Limited.
> 
> This message has been checked for all known viruses by UUNET delivered
> through the MessageLabs Virus Control Centre.
> 
> ****************************************************************************
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
> 
> 



-- 
http://www.multitask.com.au/people/dion/

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