You got a valid point here, although I'm not sure if we must bother the user by explicitly passing properties to sub-projects.
For myself I use some sort of namespacing to prevent property clashes; I prepend every property inside a project, with the projects name. So in a project with the name "foenix", I have properties called "foenix.src", "foenix.dist", etc. This way, the user can override the settings for each project, including all subproject, from the commandline, and we don't have naming conflicts between projects. Personally I like the "namespacing" approach better. My 2 cents, Arnout > -----Original Message----- > From: Ludovic Claude [mailto:[EMAIL PROTECTED] > Sent: zondag 30 januari 2000 22:14 > To: [EMAIL PROTECTED] > Subject: Properties and subprojects > > > > Still struggling with Ant & properties ... Now I came across > a problem with ant > subprojects: > By default, when you launch a subproject, all the properties > defined in the > parent project override > the subproject properties. > But if I define in the parent project a property called > src.dir, and in the > subproject a property with > the same name, they may not have the same value, so you need > to keep the > subproject value when > running it from the parent project. > I added a patch to Ant.java, so now you have a property > called properties where > you can > explicitely give the list of properties to use from the > parent project. By > default, you still have the > old behavior of using all properties from the parent project. > > You can download the new Ant.java file from > http://www.ringsys.co.uk/opensource/Ant.java > And the diff is > http://www.ringsys.co.uk/opensource/Ant.java.diff > > Ludovic Claude. > > >
