On Sunday 22 February 2004 20:55, J�rg Schaible wrote: > Niclas Hedhman wrote: > > On Sunday 22 February 2004 06:26, J�rg Schaible wrote: > >> Well, you can introduce entities in your project XML files for > >> dependencies and versions. In the end you will not have one file with > >> all versions, but a directory will all entities containing the version > >> or dependency. > > > > Works great if all versioning information sits in XML files... which > > unfortunately is not true :o/ > > What do you refer in special?
Maybe it is only me, but I typically have a large array of content that is updated over the course of a product life cycle, version of your own and other products being one. The fact that I do build a generic build system, that handles "my type" of projects, even done outside my own organization and team, means that stuff like; Company Names Product or Project Names Contact names and numbers. URLs of many types. Licensing references and inclusions. and a bunch more I can recall just off-hand... And having a list of 2 dozen "Macros" that you insert whereever you need, without having to worry how that is resolved is just great. (I even have a build system that builds build systems for customers, in this fashion.) Cheers Niclas --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
