Yes, it does not detect conflicts due to removed classes right now, 
which was previously an uncommon case until we started doing these 
removals.  So, I need to add this.  (Or if someone else wants to tinker 
with it and add this, that would be great.)  Hmm, I thought it did 
check for method removal conflicts, though.

For now, you could check for the class removal conflicts by hand...  
Let's see, I guess you could do that by simply trying to file in your 
MCP changesets into the current 3.6alpha image, and noting any messages 
like "B3DMorph is undeclared" in the transcript.  Although you will 
walkback windows too, so I guess this would be somewhat tedious.  I'll 
try to work on improving the ConflictChecker soon to handle this stuff.

- Doug Way

(p.s. I'm finally catching up on some other threads now and will reply 
to them soon...)


On Sunday, May 11, 2003, at 11:07 AM, <diegogomezdeck at consultar.com> 
wrote:

> Hi,
>
> Based on the results (only 4 conflicts between removals and MCP) seems 
> like
> ConflictChecker doesn't detect changes to removed classes or removed
> methods as conflicts.
>
> Diego
>
>> doug told me that this was good and done for what you would like to 
>> do,
>>  but I did not had the time to check.
>>
>> stef
>>
>> On Sunday, May 11, 2003, at 04:52 PM, <diegogomezdeck at consultar.com>
>> wrote:
>>
>>> Hi guys...
>>>
>>> I'm on the task of checking conflicts between MCP aproved-changes and
>>> the
>>> removals stuff.
>>>
>>> I found ConflictChecker (Doug Way) on SM and I'm wondering it'd be
>>> useful.
>>>
>>> Couple of questions:
>>>
>>> - Anyone is using it?
>>> - Which type of conflicts it detect?
>>>
>>> TIA,
>>>
>>> Diego
>
>
>