My question would be more why do your custom condition need to access
an arbitrary property. If it needs some input, it should take it in
the form of an attribute setter and use that. --DD
-
To unsubscribe, e-mail: [EMAIL PROTECTE
Hmm. to throw another iron in the fire, Ant uses
reflection to detect a setProject(oata.Project) method
on... anything. So you could just do that if you
don't want the baggage.
HTH,
Matt
--- Brian Kuhn <[EMAIL PROTECTED]> wrote:
> Yeah, I think that's the 'old' way of writing
> conditions. It's
Have you tried implementing the "setProject(oata.Project)" method? One of
the committers could say for sure, but I think the introspector will call
that method, even if the class in question does not extend from
oata.ProjectComponent...
JEC
--
Jeffrey E. Care ([EMAIL PROTECTED])
WebSphere v7 R
Yeah, I think that's the 'old' way of writing conditions. It's pretty much
like writing a task. I was hoping to extend
org.apache.tools.ant.taskdefs.condition.Equals, which extends
java.lang.Object and implements
org.apache.tools.ant.taskdefs.condition.Condition. It doesn't look like
that's going t
IIRC so long as your condition impl. class extends form
oata.ProjectComponent you can get a handle to the project. One way to do
this would be to extend oata.taskdefs.condition.ConditionBase
--
Jeffrey E. Care ([EMAIL PROTECTED])
WebSphere v7 Release Engineer
WebSphere Build Tooling Lead (Proje
Hi all,
I'm writing a custom condition that needs to get the value of a property in
the project. How do I get a reference to the project from a condition? In a
custom task, I would call this.getProject().getProperty("foo"). Since
condition is an interface, I have no such option.
Thanks,
Brian