Stefano Mazzocchi wrote, On 11/03/2003 19.53:
Christian Haul wrote:...
Strangely enough, a quick look at blocks-build.xsl seems to indicate that files in the conf directory are filtered. Hints anybody?
Yes. the <filter> indications are now located in a build.xml file located inside the block. Unfortunately, it seems that ant is not able to retain the scope of those tasks when setup in a nested antcall target, even if intra-vm.
<antcall> actually works like <ant>, and is completely reentrant. ...
the ideal solution would be to give its block the ability to define its own build customizations, but ant doesn't have this 'inheritance' concept :/
It does (at least in the version Cocoon is using IIRC), it's called <import>
Make a base-block-build.xml file, with the basic block build stuff, and in every block build do a import of that file.
You can also redefine targets, and call the original targets by prepending "projectname." to the target (where projectname is the actual project name of the base build).
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------