Ben, Thanx for the tip. I looked at and downloaded Ivy. Looks like a glove fit for what I wanted. I'm going to start simple and declare only external jar dependencies at first. As I see need I'll grow my usage of Ivy. Could you help me out with something relatively simple? I want to retreive all dependency libs in a lib folder under the build folder. I also want to parameterize the location of the repository as I have one on my local machine but would like my team to use a different repo when I check all the source in. I'm reading and experimenting to figure this out myself, just thought I'd ask to see if you or anyone else has a quick/easy answer. Thanx.
On Friday 11 November 2005 1:30 pm, Burgess, Benjamin wrote: > Before you completely reject all external tasks, you should at least > look at Ivy as it does exactly what you are describing (including > generation of tree reports showing dependencies). > http://www.jayasoft.org/ivy > > Ben > > -----Original Message----- > From: Clifton Craig [mailto:[EMAIL PROTECTED] > Sent: Friday, November 11, 2005 1:26 PM > To: user@ant.apache.org > Subject: Re: How to execute an AntCall for each property in a set > > Matt, > > Thanx for the reply. However I was looking for a more standard approach > avoiding antcontrib. I want my build to be as simple as possible without > the > need to pile on a bunch of additional library code as I took the latter > approach before and wound up in a lot of trouble down the line. I guess > I > should explain that I am basically rewriting our existing build that I > screwed up a couple of years ago when I was fresh to Ant and I'm trying > to > incorporate best practices. I question my current approach as well. I'm > sure > many would suggest <insert name of Ant alternative here> for what I'm > doing > but I'd like to stick with vanilla Ant. That's Ant sans contrib libs and > with > as little customization as possible. > > My builds (I'm using multiple builds for sub-components of our project) > should > basically auto-include all dependencies for the sub-component they > operate on > prior to starting their process. The idea is to define the properties in > a > dependencies.list file which is basically a Java properties file listing > > external libs and their equivalent version used in the sub-component. > Later > (I the distant future that may never come) I have ideas to process the > dependencies list to generate a graphical tree outlining which libs our > project depends on and where (in which component) those dependencies > occur. > I'm just trying to be smart about managing them up front rather than > just > dumping them (as we used to) in some lib folder on the filesystem and > forgetting about them. Any clues? -- Clifton C. Craig, Software Engineer Intelligent Computer Systems - A Division of GBG 2101 Embassy Drive Lancaster, PA 17603 Phone: 717-295-7977 ext. 621 Fax: 717-295-7683 [EMAIL PROTECTED] [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
