On Fri, Mar 14, 2008 at 6:17 AM, Peter Reilly
<[EMAIL PROTECTED]> wrote:
> I have a patch for macrodef which allows macrodef to have (nearly)
> arbitrary xml fragments:
>
> <macrodef name="thecommonlinks">
> <sequential>
> <!-- This part is very common : Start -->
> <link offline="true" href="http://java.sun.com/j2se/1.5.0/docs/api/";
> packagelistLoc="javadoc/j2se-1.5.0"/>
> <link offline="true" href="http://java.sun.com/javaee/5/docs/api/";
> packagelistLoc="javadoc/javaee-5"/>
> <link href="http://lab.ourserver.com/javadoc/common/"/>
> <link href="http://lab.ourserver.com/javadoc/dist/"/>
> <link href="http://lab.ourserver.com/javadoc/ejb/"/>
> <link href="http://lab.ourserver.com/javadoc/web/"/>
> </sequential>
> </macrodef>
This is great Peter, except for the name maybe. Would it be possible
to keep <macrodef> for tasks and have a separate <fragmentdef> for XML
fragments to be used inside tasks or types? <fragmentdef> then can get
rid of the nested <sequential> and doesn't accept <attribute> and
<element>?!?!
Also, if the fragment contains ${prop} and @{prop}, which context is
used to replace these (if at all), the declaration point or the use
point? --DD
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
