tried that, doesn't work.
the ${project.name} prop is introduced on the same level:
<target name="project">
<ant antfile="component_build.xml" >
<property name="project.name" value="someapp" />
<property name="httpd.${project.name}" value="httpd-bla" />
</ant>
</target>
the reference to ${project.name} on line 4 causes an error. I can't use that
reference until I'm in the component_build script.
cheers
Rob
Peter Donald wrote:
> At 02:21 26/4/01 +0200, Rob van Oostrum wrote:
> >My master build file invokes my generic app build script passing the
> >project name as a property. So the name of the property in the generic app
> >script is httpd.service.name.${project.name}
>
> How about
>
> <target name="load-properties">
> <property file="settings.${project.name}.proeprties"/>
> </target>
>
> Which loads from one of the files
>
> settings.project1.proeprties
> settings.project2.proeprties
> settings.project3.proeprties
> etc.
>
> Each file contains lines like
>
> httpd.service.name=...
> smtp.service.name=...
> ...
>
> >I'm new to the DEV list, so could somebody explain to me what the argument
> >is for not having it (other than "what's the point of having it?"). I'd be
> >more than happy to help out on the development of this, if that's what
> >it'll take.
>
> I think it has been requested before (I think I may have even sent in
> patches to get it aaaaages ago). However as it offers nothing but
> syntactical candy and can lead to complex buildfiles it probably wont be
> added.
> Cheers,
>
> Pete
>
> *-----------------------------------------------------*
> | "Faced with the choice between changing one's mind, |
> | and proving that there is no need to do so - almost |
> | everyone gets busy on the proof." |
> | - John Kenneth Galbraith |
> *-----------------------------------------------------*
|