Dominique Devienne wrote:
On 10/30/07, Stefan Bodewig <[EMAIL PROTECTED]> wrote:
On Mon, 29 Oct 2007, Steve Loughran <[EMAIL PROTECTED]> wrote:
Our solution was to add a new reference, so we can extract text from
a java static member [...]
seems to me, we could do the same with an ant resource,
<property name="expected" javaConstant="..."/>
I think it would feel more natural in property.
But then someone will want to be able to specify the classpath used to
lookup the class, so we had a nested <classpath> to <property>?. I
thought we shied away from overloading <property> anymore? Just
playing devil's advocate I guess. --DD
More to the point, if we have a resource that provides a string, it
plugs in anywhere that resources get used. It fits in very well with the
resource-centric world view, and if we already have the resource
comparison tests, then it slides in very easily indeed.
-steve
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
