Mailing-List: contact user-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Ant Users List" <user@ant.apache.org>
Received-SPF: neutral (asf.osuosl.org: local policy)
From: "Stephen McConnell" <mcconnell@dpml.net>
To: "'Ant Users List'" <user@ant.apache.org>,
	<mlybarger@gmail.com>
Subject: RE: wanted ideas for managing project build dependancies..
Date: Thu, 8 Sep 2005 00:29:43 +0930
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <a0fb11cc050907042448e84e57@mail.gmail.com>
Thread-Index: AcWznroy+DBJmrhjRsuTbZ1mzfbSOwAHZj6w
Message-Id: <20050907145946.SEHF23311.omta05sl.mx.bigpond.com@julia>


This is an anlib that adds support for transitive dependency management and
general build automation.  It's been validated on sites running over 200
related projects.

http://www.dpml.net/magic/latest

/Steve.


> -----Original Message-----
> From: Mark Lybarger [mailto:mlybarger@gmail.com] 
> Sent: Wednesday, 7 September 2005 8:54 PM
> To: Ant Users List
> Subject: wanted ideas for managing project build dependancies..
> 
> our build system is growing rapidly. we've gone from using 
> wsad to build each war/ear manually, to having ant scripts 
> for building each item, and wrapping it together with a main 
> "autobuild" project which basically checks out each sub 
> project and calls it's build. now we're looking to integrate 
> versioning into the mix. there's maybe 14 projects total, and 
> continually growning. the structure is something like:
> 
> autobuild
> project1Web
> project1
> project2Web
> project2
> 
> where project2Web is the war project, and project2 is the ear 
> project. for no good reason, we have each war wrapped into an 
> ear. this practice continues today. back on track. like i 
> mentioned, the autobuild ties everything together. it does a 
> cvs co on each project, then iterates the builds. we've 
> recently branched project2Web and project2 to allow new 
> development to happen while testing finishes up on a version 
> of project1Web and project2Web that are slated for production 
> soon. so, i'm looking for a good method for managing the cvs 
> branch dependancies of projects. 
> project1Web is still in the head, as there's no real reason 
> to branch yet. 
> one suggestion made from our group was to branch the 
> autobuild project, and in there checkin the build.xml or 
> properties file containing a list of the needed cvs branches.
> 
> any thoughts / ideas on managing the revolving cvs 
> dependancies in projects like this is much appreciated.!
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org