Page: http://wiki.cocoondev.org/Wiki.jsp?page=YourCocoonBasedProject , version:
6 on Fri Jun 27 18:01:32 2003 by MarcPortier
- __NB: I have tested this and looked at the code, and don't think this
works.__ ([GeoffHoward])
-
+
+ ''NB: I have tested this and looked at the code, and don't think this
works.'' ([GeoffHoward])
+ Completion: (as checked with Geoff) this works allright, but you have to make
sure that the property to be substituted has a value set. If not the
property-substitution will stay unchanged. And then Geoff is very right in
saying that the xpatch task will not be doing that
+ substitution for you.
+
+
+ While at it, this is another technique achieving the same:
+
+ a file mypatch.xconf in the directory ${src.xconf}
+ {{{...
+
+ <component class="@classname@" ..
+
+ ...
+ }}}
+
+
+ together with copy-token-filtering support of ant:
+ {{{
+ <mkdir dir="${cocoon-xconf.dir}" />
+ <filter token="classname" value="${component-classname}"/>
+ <copy todir="${cocoon-xconf.dir}" filtering="on" overwrite="true">
+ <fileset dir="${src.xconf}" />
+ </copy>
+ }}}
