Re: Clustered Maven?

[Rick Mangi]

FYI - the build system I described was for PV-WAVE (www.vni.com) circa 
1996. The builds ran on a dozen flavors of unix, vax and open vms. We 
did partial builds (certain components and not necessarily automated) 
on QNX, Win NT, NextStep, Linux (slackware 0.x i think) and MacOS 8 
(IIRC). It worked great. No single failure would take down the rest of 
the builds (why would they?).  This code was easily 1,000,000 lines. C, 
C++, Fortran. A similar process was used to build IMSL back then as 
well.

Shell scripts, rsh, expect, etc. aren't sexy. But sometimes they're the 
best tool for the job. I'm not knocking any of the other tools 
mentioned, I haven't used them. They might be great.

Rick
On Feb 23, 2005, at 4:01 PM, Jared Richardson wrote:

-----Original Message-----
From: Rick Mangi [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 23, 2005 3:23 PM
To: Maven Users List
Subject: Re: Clustered Maven?
Well no, not necessarily. You could just put the project
descriptors on
each machine so maven would know which SCM to connect to for each
project. It would then download src just for the projects you are
building on each machine. I'm not sure what the minimum requirements
are for this in terms of which files you need, but I imagine just
project.xml, maven.xml and project.properties. This is where
build.properties comes in very handy. You can specify machine
specific
overrides there.
I'd look at the tools Vincent mentions as well. I haven't used any of
them myself.

Thanks. This looks like the best solution so far.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]