You're scaring me, Steve - I'm working on a complex build right now
that is heavily dependent on this behavior.
In a build file fragment:
<!-- Library Properties -->
<xmlproperty file="${lib.dir}/lib-properties.xml"
keepRoot="false"
collapseattributes="false"
semanticattributes="true"
/>
Then in ${lib.dir}/lib-properties.xml:
<libraries>
<!-- Core Dependencies (Logging, etc) - Tools need'em too! -->
<commons-logging>
<version value="1.0.3"/>
<dir location="${common.lib.dist.dir}"/>
<subdir value=""/>
<dist.dir location="${commons-logging.dir}/${commons-logging.subdir}"/>
<jar.name value="commons-logging-${commons-logging.version}.jar"/>
<jar location="${commons-logging.dist.dir}/${commons-logging.jar.name}"/>
<available classname="org.apache.commons.logging.Log"/>
</commons-logging>
<!-- More lib definitions... -- >
</libraries>
Works like a charm in 1.6.2. Note that "common.lib.dist.dir" is
externally defined (in yet another XML properties file with
environmental properties in it).
Did I misunderstand your question?
Ken
At 09:34 2005-11-21, you wrote:
Why doesnt <xmlProperty> expand inline properties?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
