|
Re: Target platform problem [message #507125 is a reply to message #501206] |
Tue, 12 January 2010 04:26 |
Lo�¯c Qu�©ran Messages: 45 Registered: July 2009 |
Member |
|
|
Hi,
I have exactly the same problem with net.sourceforge.lpg.lpgjavaruntime
being provided by various locations (cdt-master-5.0.2, gmf-sdk-2.1.3,
mdt-ocl-SDK-1.2.3). When launched directly, the target platform works
normally. When editing the target content and showing the plugin content
(Preferences->Plug-in Development->Target
Platform->Edit...->Locations->Show Plug-in Content), the plugin appears.
But in the Plug-ins view, it does not appear and when an Eclipse
application is launched with "all workspace and enabled target
plug-ins", it misses required bundle net.sourceforge.lpg.lpgjavaruntime.
Loïc
Lothar Werzinger wrote:
> Hi,
>
> If I define a target platform with multiple locations (e.g. for RAP) and the
> locations contain the same plugin in either the same or a different version
> number then the resulting target platform does not work and creates either
> compile or runtime errors, as the duplicate plugins are not available at
> all in the target platform.
>
> I tried all combinations of locations (directory, installation, update site)
> but I can not create a working target platform. As a workaround I deleted
> the duplicate plugins from the RAP directory location, but I think this may
> be a bug of PDE. Does anyone know more about this behavior? I can't believe
> that I am the only one experiencing problems if this is a general problem
> with target platforms.
>
> I have attached my target definition and a screenshot showing that eclipse
> can't find org.eclipse.core.runtime and that is part of the target
> definition (twice).
>
> Thanks in advance!
>
> Lothar
>
>
> ------------------------------------------------------------ ------------
>
|
|
|
Re: Target platform problem [message #507328 is a reply to message #507125] |
Tue, 12 January 2010 22:54 |
Lothar Werzinger Messages: 153 Registered: July 2009 Location: Bay Area |
Senior Member |
|
|
Loïc Quéran wrote:
> Hi,
>
> I have exactly the same problem with net.sourceforge.lpg.lpgjavaruntime
> being provided by various locations (cdt-master-5.0.2, gmf-sdk-2.1.3,
> mdt-ocl-SDK-1.2.3). When launched directly, the target platform works
> normally. When editing the target content and showing the plugin content
> (Preferences->Plug-in Development->Target
> Platform->Edit...->Locations->Show Plug-in Content), the plugin appears.
> But in the Plug-ins view, it does not appear and when an Eclipse
> application is launched with "all workspace and enabled target
> plug-ins", it misses required bundle net.sourceforge.lpg.lpgjavaruntime.
>
> Loïc
>
>
> Lothar Werzinger wrote:
>> Hi,
>>
>> If I define a target platform with multiple locations (e.g. for RAP) and
>> the locations contain the same plugin in either the same or a different
>> version number then the resulting target platform does not work and
>> creates either compile or runtime errors, as the duplicate plugins are
>> not available at all in the target platform.
Moving to the latest milestone (M4) of Helios solved the problem for me. If
you can use Helios then that may be the fastest way to get things working.
I don't know if there are any plans to backport the fix to Galileo.
Lothar
|
|
|
Re: Target platform problem [message #604098 is a reply to message #501206] |
Tue, 12 January 2010 09:27 |
Lo�¯c Qu�©ran Messages: 45 Registered: July 2009 |
Member |
|
|
Hi,
I have exactly the same problem with net.sourceforge.lpg.lpgjavaruntime
being provided by various locations (cdt-master-5.0.2, gmf-sdk-2.1.3,
mdt-ocl-SDK-1.2.3). When launched directly, the target platform works
normally. When editing the target content and showing the plugin content
(Preferences->Plug-in Development->Target
Platform->Edit...->Locations->Show Plug-in Content), the plugin appears.
But in the Plug-ins view, it does not appear and when an Eclipse
application is launched with "all workspace and enabled target
plug-ins", it misses required bundle net.sourceforge.lpg.lpgjavaruntime.
Loïc
Lothar Werzinger wrote:
> Hi,
>
> If I define a target platform with multiple locations (e.g. for RAP) and the
> locations contain the same plugin in either the same or a different version
> number then the resulting target platform does not work and creates either
> compile or runtime errors, as the duplicate plugins are not available at
> all in the target platform.
>
> I tried all combinations of locations (directory, installation, update site)
> but I can not create a working target platform. As a workaround I deleted
> the duplicate plugins from the RAP directory location, but I think this may
> be a bug of PDE. Does anyone know more about this behavior? I can't believe
> that I am the only one experiencing problems if this is a general problem
> with target platforms.
>
> I have attached my target definition and a screenshot showing that eclipse
> can't find org.eclipse.core.runtime and that is part of the target
> definition (twice).
>
> Thanks in advance!
>
> Lothar
>
>
> ------------------------------------------------------------ ------------
>
|
|
|
Re: Target platform problem [message #604109 is a reply to message #604098] |
Tue, 12 January 2010 22:54 |
Lothar Werzinger Messages: 153 Registered: July 2009 Location: Bay Area |
Senior Member |
|
|
Loïc Quéran wrote:
> Hi,
>
> I have exactly the same problem with net.sourceforge.lpg.lpgjavaruntime
> being provided by various locations (cdt-master-5.0.2, gmf-sdk-2.1.3,
> mdt-ocl-SDK-1.2.3). When launched directly, the target platform works
> normally. When editing the target content and showing the plugin content
> (Preferences->Plug-in Development->Target
> Platform->Edit...->Locations->Show Plug-in Content), the plugin appears.
> But in the Plug-ins view, it does not appear and when an Eclipse
> application is launched with "all workspace and enabled target
> plug-ins", it misses required bundle net.sourceforge.lpg.lpgjavaruntime.
>
> Loïc
>
>
> Lothar Werzinger wrote:
>> Hi,
>>
>> If I define a target platform with multiple locations (e.g. for RAP) and
>> the locations contain the same plugin in either the same or a different
>> version number then the resulting target platform does not work and
>> creates either compile or runtime errors, as the duplicate plugins are
>> not available at all in the target platform.
Moving to the latest milestone (M4) of Helios solved the problem for me. If
you can use Helios then that may be the fastest way to get things working.
I don't know if there are any plans to backport the fix to Galileo.
Lothar
|
|
|
Powered by
FUDForum. Page generated in 0.02743 seconds