Wow! What a good idea!
This lets XDoclet users configure the outcome of XDoclet on the
build.xml level, right?
I recommend people using this feature put the properties in a separate
properties file, and having Ant read that in. That way, the
configuration is moved out even one level furter, namely to a
properties file. For the Ant users who are not familiar with this
technique:
<property file="jboss.properties"/>
And the contents of the jboss.properties file would be:
jboss.create.table=true
jboss.remove.table=true
jboss.tuned.updates=true
jboss.read.only=false
That way, the values can be altered without having to edit the
build.xml file.
<aslak/>
----- Original Message -----
From: Dmitri Colebatch <[EMAIL PROTECTED]>
Date: Thursday, October 4, 2001 1:19 pm
Subject: [Xdoclet-devel] using ant properties in tags
> I've just committed a change that lets you use ant properties in tag
> values. THere's a pretty simple example in Account:
>
> * @jboss:table-name "account"
> * @jboss:create-table "${jboss.create.table}"
> * @jboss:remove-table "${jboss.remove.table}"
> * @jboss:tuned-updates "${jboss.tuned.updates}"
> * @jboss:read-only "${jboss.read.only}"
>
> where the corresponding values are defined in the build.xml
>
> <!-- These are here to test the use of properties in @tags -->
> <property name="jboss.create.table" value="true" />
> <property name="jboss.remove.table" value="true" />
> <property name="jboss.tuned.updates" value="true" />
> <property name="jboss.read.only" value="false" />
>
> Jason - let me know if this does the trick
>
> cheers
> dim
>
>
> _______________________________________________
> Xdoclet-devel mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
>
_______________________________________________
Xdoclet-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
