[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cdt-dev] Build errors in master - ITreeModelContentProviderTarget
|
We are OK for now. With Pawel's patch, the code works in both Indigo and Juno. We will deal with the warnings later.
Eugene
-----Original Message-----
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Jeff Johnston
Sent: Monday, December 12, 2011 4:53 PM
To: cdt-dev@xxxxxxxxxxx
Subject: Re: [cdt-dev] Build errors in master - ITreeModelContentProviderTarget
Upon thinking about it for a few more seconds, there should be a separate branch.
On 12/12/2011 07:48 PM, Jeff Johnston wrote:
> The patch could be rewritten to use reflection so that it tests for
> the methods that are found in Juno and these tests will work under Indigo.
> The other choice is to create a separate branch for Juno.
>
> -- Jeff J.
>
> On 12/12/2011 07:24 PM, Tarassov, Eugene wrote:
>> It does not work in 3.7.1:
>> The method getTreeModelViewer() is undefined...
>>
>> Eugene
>>
>> -----Original Message-----
>> From: cdt-dev-bounces@xxxxxxxxxxx
>> [mailto:cdt-dev-bounces@xxxxxxxxxxx]
>> On Behalf Of Jeff Johnston
>> Sent: Monday, December 12, 2011 4:15 PM
>> To: CDT General developers list.
>> Cc: TCF Development (tcf-dev@xxxxxxxxxxx)
>> Subject: Re: [cdt-dev] Build errors in master -
>> ITreeModelContentProviderTarget
>>
>> Would the attached patch1 work? The patch uses the TreeModelViewer to
>> find the paths for the launch object and sets found if there are any
>> tree paths found. The code was initially assuming there was a Tree
>> control and it was looking at the items for launch. That code was
>> changed as part of
>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=349998
>>
>> -- Jeff J.
>>
>>
>> On 12/12/2011 01:08 PM, Schaefer, Doug wrote:
>>> Hey gang,
>>>
>>> I've attempted our first build of CDT and TCF masters against
>>> Eclipse
>>> 4.2 and found a number of build errors.
>>> ITreeModelContentProviderTargetappears to be gone (or did it move?).
>>> I see lots of references on the cdt.tests.dsf plug-in. I also see it
>>> being used in the tcf.debug.ui plugin which is a bit more concerning.
>>> And either way, this was an internal class we should never have been
>>> using to begin with.
>>>
>>> Does anyone have an idea on how to address this?
>>>
>>> Thanks,
>>>
>>> Doug.
>>>
>>>
>>>
>>> _______________________________________________
>>> cdt-dev mailing list
>>> cdt-dev@xxxxxxxxxxx
>>> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>>
>> _______________________________________________
>> cdt-dev mailing list
>> cdt-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>>
>
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
