Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] unresolved references to org.eclipse.remote

I don't know why that messages was displayed. The pde version in the
file is the same as the target defined with Kepler SR2. I think it's
safe to ignore.

Marc-Andre

On 14-05-08 02:04 AM, Nathan Ridge wrote:
> That seems to have fixed the problem - the 4.4 target now
> seems to load correctly, and the errors about 
> org.eclipse.remote are gone. Thanks!
>
> I did get a message saying:
>
> "You have selected a target with a newer version than your 
> current Eclipse installation. This can cause unexpected 
> behaviour in PDE. Please use a newer version of Eclipse."
>
> I guess this is safe to ignore? My Eclipse installation
> is 4.3.2.
>
> Thanks,
> Nate
>
>
>
> ----------------------------------------
>> From: marc-andre.laperle@xxxxxxxxxxxx
>> To: cdt-dev@xxxxxxxxxxx
>> Date: Thu, 8 May 2014 05:18:55 +0000
>> Subject: Re: [cdt-dev] unresolved references to org.eclipse.remote
>>
>> org.eclipse.remote.feature.group had a version specified that didn't exist anymore. I changed it to 0.0.0 so that it picks whatever is available at that update site. You can try to reopen the target definition file again and everything should resolve properly.
>>
>> Not that it really matters in this case but I just want to note that when using 0.0.0, if the update site happens to have multiple versions, it *should* pick the latest but it's not guaranteed to pick the latest unless you use>= 4.4-I20140427-2030, see https://bugs.eclipse.org/bugs/show_bug.cgi?id=432375.
>>
>> Marc-Andre
>>
>> ________________________________________
>> From: cdt-dev-bounces@xxxxxxxxxxx [cdt-dev-bounces@xxxxxxxxxxx] on behalf of Nathan Ridge [zeratul976@xxxxxxxxxxx]
>> Sent: Wednesday, May 07 2014 8:55 PM
>> To: CDT Mailing List
>> Subject: Re: [cdt-dev] unresolved references to org.eclipse.remote
>>
>>>> I tried setting the target to 4.4, but it made things worse. It made my
>>>> project go from having 75 errors (related to org.eclipse.remote) to
>>>> having> 120000 errors, about everything from junit to org.eclipse.core.
>>>>
>>>> Setting the target back to 4.3 brings me back to a state where I just
>>>> have the 75 errors related to org.eclipse.remote.
>>>>
>>>> I notice that if I go to Window -> Preferences -> Plug-in Development ->
>>>> Target Platform, select cdt_e4.4 and click "Reload", I get an error
>>>> saying
>>>>
>>>> Problems were found with the selected target definition. You can
>>>> still set the definition as the active target, but there may be
>>>> problems building.
>>>>
>>>> Reason:
>>>> Problems occurred getting the plug-ins in this container.
>>>>
>>>> Details:
>>>> Unable to locate installable unit org.eclipse.remote.feature.group
>>>>
>>>> Any ideas on how to fix this?
>>> It seems you have the problem documented in
>>> the Bug
>>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=430655
>>>
>>> The work around from Marc-Andre mentions a sequence number,
>>> you will find this element in the second line of the target definition file,
>> Unfortunately, that workaround did not fix the problem.
>>
>> Also, there was no "switch of network environments" in my case.
>>
>> I guess I have a different problem, just not sure what it is.
>> Any suggestions are welcome.
>>
>> Thanks,
>> Nate
>>
>> _______________________________________________
>> 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



Back to the top