RE: [Nant-users] any suggested strategies for an environment where new project dependencies are constantly being added?

[Thomas Tomiczek]

Yeah, this is a severe issue, and I am looking into this, too, at the moment.

 

I have a similar issue. We have a set of products that we maintain - products are totally separate development cycles, but may consist of more than one solution. So far thing are rally easy, in that I do have a solutions directory with a subdirectory per solution, and running the nant-script-thing is easy enough.

 

Problems get injected as products are coupled - one product_s output may be used in the next product as input (base library), especially as, along the product lines, we have an application framework and an O/R mapper among the products, havingbasically a100% reuse rate.

 

Things are really tricky at this level - so far I am missing any sort of white paper for how to handle such complex build scenarios. We are slowly developing our own toolset/best practices for this, but it is a painful approach so far, especially when going upward and integrating, further, things like cruise control. Plus a set of less than sensible products, resulting in some really "interesting" structure of the directory in the source control system (ok, this is mostly the fault of the documentation tool we use and it's inability to accept a ".." in relative paths, which means the whole documentation thing is sitting in the product root, includin four mandatory sub-directories - I hate it.).

 

For your basic dependancies I would really go with an as fully automated as possible approach. I mean, our own build scripts build solutions (never projects), and they automatically build all solutions in the "Solutions" folder of a product. The minimum dependant project thing seems to be missing, though.

 

Thomas

---

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of " "
Sent: Donnerstag, 5. Mai 2005 00:47
To: nant-users@lists.sourceforge.net
Subject: [Nant-users] any suggested strategies for an environment where new project dependencies are constantly being added?

Hello,

 

Any suggested tactics to deal with this?  sorry for the newbie question but i've been looking around for some documented advice and haven't found any luck so far.

 

My problem is that we are constantly introducing new projects and new dependencies.  It seems like maintaining a buildfile in such an environment is going to be a nightmare.  I've been trying out the Nant "Solution" task and tried chaining project buildfiles that mimic the current dependencies so if someone introduces a dependency in a commonly used project, I just need to add that new dependency in 1 location and the new dependency will propogate to higher level buildfiles, but I’m not having any luck.

 

One of the nice things with Visual Studio Solutions was how a user could selectively build a project and Visual Studio would figure out all the relevant dependent projects from all possible dependent projects included in the solution file

 

Is there any similar capability in Nant where you can specify the main project that is required + a list of all possible dependent projects?  From the list of all possible dependent projects Nant could dynamically figure out the minimum dependent projects to compile.  Is something like this currently possible in Nant?

 

If my above idea isn’t doable does anybody have any other suggested tactics on how to tackle a build environment where new cs project dependencies are constantly added in a very fast paced environment?

 

thanks in advance

Joon

---

Yahoo! Mail Mobile
Take Yahoo! Mail with you! Check email on your mobile phone.