|
| Re: Delta pack not working in 3.5 [message #336589 is a reply to message #336587] |
Wed, 24 June 2009 15:42   |
Eclipse User |
|
|
|
Originally posted by: phillipus.nowhere.net
Phillipus wrote:
> Unzip the 3.5 Delta pack onto 3.5 installation.
>
> No go. It doesn't show up.
>
> What happened?
OK, I think what's changed in 3.5 is that you can no longer unzip the
Delta pack over your Eclipse installation and it work. I've always done
this before in 3.3 and 3.2 (that's why it's a Delta pack, right?). Unzip
it into a separate folder and then add that to your PDE target setup.
|
|
|
|
| Re: Delta pack not working in 3.5 [message #336591 is a reply to message #336590] |
Wed, 24 June 2009 15:55 |
| Eclipse User |
|
|
|
Originally posted by: phillipus.nowhere.net
Tom Schindl wrote:
> Hi,
>
> IMHO it was never meant to be unzipped above the installation but to use
> in your PDE-Target. Your eclipse installation doesn't need the
> additional fragments you get with the Delta-Pack because it's only
> purpose is to run the current Eclipse-Instance you use for editing.
>
> PDE by default points to the Eclipse-Installation as the target but
> that's simply to help people who only do Eclipse-Plugin development to
> install a secondary target because they rarely need to export for a
> specific platform.
>
> Tom
>
> Phillipus schrieb:
>> Phillipus wrote:
>>> Unzip the 3.5 Delta pack onto 3.5 installation.
>>>
>>> No go. It doesn't show up.
>>>
>>> What happened?
>> OK, I think what's changed in 3.5 is that you can no longer unzip the
>> Delta pack over your Eclipse installation and it work. I've always done
>> this before in 3.3 and 3.2 (that's why it's a Delta pack, right?). Unzip
>> it into a separate folder and then add that to your PDE target setup.
True, true, true. :-) It always worked though.
|
|
|
| Re: Delta pack not working in 3.5 [message #336594 is a reply to message #336591] |
Wed, 24 June 2009 17:25 |
 Andrew Niefer
Messages: 990
Registered: July 2009 |
Senior Member |
|
|
Phillipus wrote:
> Tom Schindl wrote:
>> Hi,
>>
>> IMHO it was never meant to be unzipped above the installation but to use
>> in your PDE-Target. Your eclipse installation doesn't need the
>> additional fragments you get with the Delta-Pack because it's only
>> purpose is to run the current Eclipse-Instance you use for editing.
>>
>> PDE by default points to the Eclipse-Installation as the target but
>> that's simply to help people who only do Eclipse-Plugin development to
>> install a secondary target because they rarely need to export for a
>> specific platform.
>>
>> Tom
>>
>> Phillipus schrieb:
>>> Phillipus wrote:
>>>> Unzip the 3.5 Delta pack onto 3.5 installation.
>>>>
>>>> No go. It doesn't show up.
>>>>
>>>> What happened?
>>> OK, I think what's changed in 3.5 is that you can no longer unzip the
>>> Delta pack over your Eclipse installation and it work. I've always done
>>> this before in 3.3 and 3.2 (that's why it's a Delta pack, right?). Unzip
>>> it into a separate folder and then add that to your PDE target setup.
>
>
> True, true, true. :-) It always worked though.
>
It always used to work in 3.3 and earlier because the
org.eclipse.update.configurator was promiscuous. All bundles/fragments
there were found were installed regardless whether or not they would
actually work.
Now, with dropins, things are only going to get installed if they will
actually be resolvable in the running instance. In the case of the
deltapack, the majority of the fragments will not be resolvable because
they are the wrong platform. This was the source of the "Build target
based on the target's installed plug-ins" preference that needed to be
unchecked in 3.4
To make matters worse, there is a problem with the new publisher stuff
that creates metadata for things in the dropins folder. It screws up on
the equinox.executable feature (bug 278086).
|
|
|
| Re: Delta pack not working in 3.5 [message #336596 is a reply to message #336594] |
Wed, 24 June 2009 17:28 |
| Eclipse User |
|
|
|
Originally posted by: phillipus.nowhere.net
Andrew Niefer wrote:
> Phillipus wrote:
>> Tom Schindl wrote:
>>> Hi,
>>>
>>> IMHO it was never meant to be unzipped above the installation but to use
>>> in your PDE-Target. Your eclipse installation doesn't need the
>>> additional fragments you get with the Delta-Pack because it's only
>>> purpose is to run the current Eclipse-Instance you use for editing.
>>>
>>> PDE by default points to the Eclipse-Installation as the target but
>>> that's simply to help people who only do Eclipse-Plugin development to
>>> install a secondary target because they rarely need to export for a
>>> specific platform.
>>>
>>> Tom
>>>
>>> Phillipus schrieb:
>>>> Phillipus wrote:
>>>>> Unzip the 3.5 Delta pack onto 3.5 installation.
>>>>>
>>>>> No go. It doesn't show up.
>>>>>
>>>>> What happened?
>>>> OK, I think what's changed in 3.5 is that you can no longer unzip the
>>>> Delta pack over your Eclipse installation and it work. I've always done
>>>> this before in 3.3 and 3.2 (that's why it's a Delta pack, right?).
>>>> Unzip
>>>> it into a separate folder and then add that to your PDE target setup.
>>
>>
>> True, true, true. :-) It always worked though.
>>
>
> It always used to work in 3.3 and earlier because the
> org.eclipse.update.configurator was promiscuous. All bundles/fragments
> there were found were installed regardless whether or not they would
> actually work.
>
> Now, with dropins, things are only going to get installed if they will
> actually be resolvable in the running instance. In the case of the
> deltapack, the majority of the fragments will not be resolvable because
> they are the wrong platform. This was the source of the "Build target
> based on the target's installed plug-ins" preference that needed to be
> unchecked in 3.4
>
> To make matters worse, there is a problem with the new publisher stuff
> that creates metadata for things in the dropins folder. It screws up on
> the equinox.executable feature (bug 278086).
Thanks for the info!
|
|
|
Powered by
FUDForum. Page generated in 0.03507 seconds
] 
Search
Help
Register
Login
Home
