Re: Can anybody explain somewhat confusing ant property and j:setinteraction?

[Colin Sampaleanu]

On further investigation, I am wrong in that using <property> and <j:set> do actaully behave the same. I am still confused about why having a value in my own project.properties allows me to override the plugin's value (and my own value from my prop file), but otherwise the setting is local (to the preGoal), and the plugin uses it's own default value.

Colin Sampaleanu wrote:

I am somewhat confused about how ant properties and values set via jelly:core's 'set' tag work.

The xdoclet plugin has a property, call it 'x', that is set by default in its project.properties file. I need to override this, which I am attempting to do in a preGoal in my maven.xml file.

if I do
<property name="x" value="y"/>
in the pregoal, this will always override the default plugin property.

(As would be expected, if I have a value in my project.properties for x (and nowhere else), that also overrides the default plugin property.)

but if I do
<j:set var="x" value="y"/>
then if there is no value for x in my project.properties, the set seems to have no effect, and the plugin's default value is used, while if there is a value for x in my project.properties file, then the set _does_ seem to have an effect, and the value is set as above.

I don't understand this last bit of behavior. What is the existence of a setting for x in my project properties have to do with whether or not I can later override x with a j:set in jelly code?

Regards, Colin

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>