On 3/28/07, Maarten Coene <[EMAIL PROTECTED]> wrote:
ok, I'll try the XSLT way, but I'm afraid it won't be easy to detect the modH dependency
Yes, maybe XSLT isn't really the best language for that, using a language with good function support would make it quite easy with some recursive functions. Maybe you should better go with java or a script language like ruby or groovy, depending on when you need to get this information... But it's only my feeling and it mainly depends on your skills and what you prefer :-) - Xavier Maarten
----- Original Message ---- From: Xavier Hanin <[EMAIL PROTECTED]> To: [email protected] Sent: Wednesday, March 28, 2007 5:34:55 PM Subject: Re: selecting dependencies used by only 1 module On 3/28/07, Maarten Coene <[EMAIL PROTECTED]> wrote: > > Hi, > > say I have the following modules: > > modA depends on modB and modC. > modB depends on modD, modE and modF > modC depends on modD, modF and modG > modE depends on modG and modH > > I do a resolve of all the dependencies of modA. > > Without doing a new resolve, is there a way to select all dependencies of > modB that are required for modB ONLY? In this example, this would be modE > and modH. The resolve report has all the information you need, but there is no current task to do what you want, so you'll need to write some xslt or java (if you use the ResolveReport instance which is kept in the Ant project) to get what you need. - Xavier regards, > Maarten > > > > > > > ____________________________________________________________________________________ > Bored stiff? Loosen up... > Download and play hundreds of games for free on Yahoo! Games. > http://games.yahoo.com/games/front > ____________________________________________________________________________________ Be a PS3 game guru. Get your game face on with the latest PS3 news and previews at Yahoo! Games. http://videogames.yahoo.com/platform?platform=120121
