OK I have done "something".
for taskdef-test.xml I have added 5 properties test1.jar to test5.jar
which correspond to work entries in gump.
I have seen that the java resources like ${java:foo!foo.properties} in
replacetokens-test.xml do not lend themselves to standardisation.
I wanted to replace ${java:foo!foo.properties} with
${java:${resources}!foo.properties} but we would need to have the props
antlib in ant somehow for that to work.
Hopefully this will work.
When I started to do these changes, I had forgotten to tell my IDE not
to create tabs. So after the fact I went chasing tabs in the complete
directory src/tests/antunit.
Regards,
Antoine
On 2/28/11 11:29 AM, Antoine Levy-Lambert wrote:
> On 2/28/11 11:02 AM, Stefan Bodewig wrote:
>> On 2011-02-28, Antoine Levy-Lambert wrote:
>>
>>> I see now that in fact there are still 21 antunit tests failing in gump
>>> (see [1] and [2] below) :
>>> Do we want to add a work entry in gump metadata for each of the
>>> directories where these tests create classes or resources ?
>>> Or do we want to somehow standardize and have a convention that the
>>> tests will use for instance <work
>>> nested="src/tests/antunit/taskdefs/tempresources"/> and then change both
>>> the tests and the gump descriptor ?
>> I'd favor a single resource directory from a maintenance POV.
>>
>> Stefan
>>
> OK. I will straighten that up hopefully in the next 24 hours.
>
> Regards,
>
> Antoine
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
