Diego could we use those scripts too? Is it automated?
tell me more.
Stef


On Tuesday, June 3, 2003, at 11:40 AM, <diegogomezdeck at consultar.com> 
wrote:

> Hi Stef,
>
> We suffered exactly the same problem with MCP and we "solve" it with
> scripts that get the list of removed classes (from the changesets) and 
> we
> create a second changeset with the modifications we made to the 
> removed-
> stuff.
>
> We spent a *lot* of time to do that.
>
> One posible solution is to create more tools for our work.
>
> The other solution is to pause the removals for a while.
>
> Cheers,
>
> Diego
>
>> Hi
>>
>> We produced KCP change but we were modifying classes that are now
>> removed from 3.6.
>> So this leads to load errors. We could tediously discard the changes
>> from the changesets but
>> this would be a pity because we would introduce a lot of errors in
>> external packages.
>>
>> Now I was thinking that we are doing too much in the same time.
>> Cleaning in a closed world assumption is much easier
>> than in presence of removal.
>>
>> So now that we are following this path, I think that the best way to
>> continue would be to
>> have a script loading all the packages that will be present in the 3.6
>> full image and that the cleaners
>> works on this image.
>>
>> What will be absolutely important for the future is to have package (a
>> class knowing which class and methods it contains), this way (except
>> for class extensions made from one package to another one), we could
>> make that each
>> change related to a given package goes into the right package.
>>
>> Tell me what you think about that.
>>
>> Stef
>
>
>
>