I'm not fussy about the syntax but I do not want to bind the filtering to Ant.
Why don't we keep @...@ syntax by default, but allow configuration (as does Ant). I think we can reuse the POM definition to configure Ant filtersets for those that want to use it, but if we remove <resources:copy/> and replace it with a Java class, then that class can still use these tags in the same way. I think we need to specify files to load filters from, and perhaps token/value pairs in the POM for simpler cases. Both can work.
IMHO the fact that you have Ant underlying has been the most powerful aspect of Maven, and has made it so useful in our environment. While I understand the difficulties being had with Jelly, it is adding something very useful.
Cheers, Brett
-- Web Developer f2 network ~ everything essential 02 8596 4437
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
