[aspectwerkz-dev] Re: [aspectwerkz-user] Re: problems with ant task

Quote [Alexandre Vasseur]:

> the goal I had in mind was precisely to *avoid* this VM fork (no
> matter if using Ant API or not) unless really necessary (might be for
> some dependancies clashes - don't know).
> Alex
> (can we move this discussion to dev@ mailing list)

I couldn't read this between the lines [sigh/]. Than the change will be an easy one. Back to you 
with the new version soon (today).

./the_mindstorm

> 
> 
> 
> 
> On Tue, 05 Oct 2004 10:23:12 +0300, the_mindstorm
> <[email protected]> wrote:
> 
>>Quote [Alexandre Vasseur]:
>>
>>>Isn't it possible to avoid the use of the Java sub task programmatically ?
>>>I fear such an implementation will lead us to trouble - f.e. if I
>>>change an arg, it is difficult to be sure I change it there etc.
>>>Moreover avoiding this would allow to add some more things easiliy
>>>(f.e. generate some javadoc or xml things when offline weaving is
>>>performed sort of a report or alike etc.)
>>
>>I guess the single problem with changing the Java task would be to start another JVM. I will give it
>>a try in the evening and come back with the new solution.
>>
>>./the_mindstorm
>>
>>
>>
>>
>>>+1 for fileset
>>>
>>>Else, this work is more than welcome !
>>>
>>>Alex
>>>
>>
>>
>