|
@@ -23,12 +23,12 @@ had to create special attributes:<P> |
|
|
<copy file="foo" tofile="bar" head="10" contains="blee"/> |
|
|
<copy file="foo" tofile="bar" head="10" contains="blee"/> |
|
|
</code><P> |
|
|
</code><P> |
|
|
The obvious problem thus surfaced: Ant tasks would not be able |
|
|
The obvious problem thus surfaced: Ant tasks would not be able |
|
|
to accomodate such data transformation attributes as they would |
|
|
|
|
|
|
|
|
to accommodate such data transformation attributes as they would |
|
|
be endless. The task would also not know in which order these |
|
|
be endless. The task would also not know in which order these |
|
|
attributes were to be interpreted. That is, must the task execute the |
|
|
attributes were to be interpreted. That is, must the task execute the |
|
|
contains attribute first and then the head attribute or vice-versa? |
|
|
contains attribute first and then the head attribute or vice-versa? |
|
|
What Ant tasks needed was a mechanism to allow pluggable filter (data |
|
|
What Ant tasks needed was a mechanism to allow pluggable filter (data |
|
|
tranformer) chains. Ant would provide a few filters for which there |
|
|
|
|
|
|
|
|
transformer) chains. Ant would provide a few filters for which there |
|
|
have been repeated requests. Users with special filtering needs |
|
|
have been repeated requests. Users with special filtering needs |
|
|
would be able to easily write their own and plug them in.<P> |
|
|
would be able to easily write their own and plug them in.<P> |
|
|
|
|
|
|
|
@@ -1344,4 +1344,4 @@ This may be used as follows: |
|
|
<HR> |
|
|
<HR> |
|
|
|
|
|
|
|
|
<P align=center>Copyright © 2002-2003 Apache Software Foundation. All rights |
|
|
<P align=center>Copyright © 2002-2003 Apache Software Foundation. All rights |
|
|
Reserved.</P></BODY></HTML> |
|
|
|
|
|
|
|
|
Reserved.</P></BODY></HTML> |