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 [EMAIL PROTECTED] On Friday 11 November 2005 12:33 pm, Matt Benson wrote: > Hmm... Ant 1.7 in combination with antcontrib <for> is > designed to support this. Assuming you have to use > production releases, I would write either: > > (a) a custom task to convert a property set to a list > or > (b) a custom type to wrap a PropertySet ps, with > public Iterator iterator() { > return ps.getProperties().values().iterator(); > } > > I would pass the result to <for> in either case. (b) > would ultimately be similar to the way Ant 1.7 works. > > HTH, > Matt > > --- Clifton Craig <[EMAIL PROTECTED]> wrote: > > I need to iterate a propertyset which lists a > > project's dependencies. It's > > basically just a list of name/val pairs matching a > > 3rd party product (or open > > source jar) with a version. I want to execute an > > Antcall or something of the > > like to ask our jar repository for the proper jar > > file so the build can > > procede after the dependencies have been met. Any > > good advice on this? Thanx > > in advance! > > > > -- > > Clifton C. Craig, Software Engineer > > [EMAIL PROTECTED] > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: > > [EMAIL PROTECTED] > > For additional commands, e-mail: > > [EMAIL PROTECTED] > > __________________________________ > Yahoo! Mail - PC Magazine Editors' Choice 2005 > http://mail.yahoo.com > > --------------------------------------------------------------------- > 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] ************************************************************** This message, including any attachments, contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, please contact sender immediately by reply e-mail and destroy all copies. You are hereby notified that any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited. TIAA-CREF ************************************************************** --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
