| UI artefacts after installing of features into buckminster [message #702643] |
Tue, 26 July 2011 15:50  |
Eclipse User |
|
|
|
Originally posted by: Ralf Zozmann
Hi @all,
currently i'm trying to update our build process from bucky 3.6 to the
Eclipse 3.7 based variant.
We are using buckminster also as host for some code generation tasks
while the build process. So i have to install additional features into
the headless buckminster (org.eclipse.buckminster.cmdline.product
1.4.0.v20110629-1242). All the headless features coming from the
buckminster sites seems to be ok (means
org.eclipse.buckminster.core.headless.feature,
org.eclipse.buckminster.subversive.headless.feature, ...).
But the simpelst additional feature i try to install does come with UI
bundles at the end. As example: Installing the 'org.eclipse.emf.common'
feature (via scipt using the buckminster 'install' command) will also
install org.eclipse.ui, org.eclipse,swt, org.eclipse.jface,....
Looking into the feature.xml and the dependencies for
'org.eclipse.emf.common' only 'org.eclipse.core.runtime' is requested.
Currently i have no idea why these bundles are materialized, but i have
trouble from the presence.
Can anybody help me to understand that phenomenon so i can work around?
Thanks
Ralf
|
|
|
| Re: UI artefacts after installing of features into buckminster [message #703113 is a reply to message #702643] |
Wed, 27 July 2011 06:55  |
| Eclipse User |
|
|
|
Originally posted by: Ralf Zozmann
Morning,
after some more investigation i doesn't longer believe that this is a
problem related to buckminster, but something wrong this the used update
sites. Using my example (installing feature org.eclipse.emf.common) from
yesterday:
If i install the feature from
http://download.eclipse.org/modeling/emf/updates/releases/ then all is
ok, but if i use the update site
http://download.eclipse.org/releases/indigo/ i got all the ui bundles as
result.
Strange! Mmhhh.. is this in any way related to the circular dependency
problem of JDT->UI, but in a different bundle (one more patch affecting
a normally headless plugin)?
Regards
Ralf
On 07/26/2011 05:50 PM, Ralf Zozmann wrote:
> Hi @all,
>
> currently i'm trying to update our build process from bucky 3.6 to the
> Eclipse 3.7 based variant.
> We are using buckminster also as host for some code generation tasks
> while the build process. So i have to install additional features into
> the headless buckminster (org.eclipse.buckminster.cmdline.product
> 1.4.0.v20110629-1242). All the headless features coming from the
> buckminster sites seems to be ok (means
> org.eclipse.buckminster.core.headless.feature,
> org.eclipse.buckminster.subversive.headless.feature, ...).
>
> But the simpelst additional feature i try to install does come with UI
> bundles at the end. As example: Installing the 'org.eclipse.emf.common'
> feature (via scipt using the buckminster 'install' command) will also
> install org.eclipse.ui, org.eclipse,swt, org.eclipse.jface,....
> Looking into the feature.xml and the dependencies for
> 'org.eclipse.emf.common' only 'org.eclipse.core.runtime' is requested.
> Currently i have no idea why these bundles are materialized, but i have
> trouble from the presence.
> Can anybody help me to understand that phenomenon so i can work around?
>
> Thanks
> Ralf
|
|
|
| Re: UI artefacts after installing of features into buckminster [message #703168 is a reply to message #703113] |
Wed, 27 July 2011 08:11 |
|
Hi Ralf,
On 2011-07-27 08:55, Ralf Zozmann wrote:
> Strange! Mmhhh.. is this in any way related to the circular dependency
> problem of JDT->UI, but in a different bundle (one more patch affecting
> a normally headless plugin)?
>
I don't think it's the same problem since that was related to a limitation in Buckminsters resolver. When you install,
the p2 planner is in charge and it wouldn't make the same mistake. A more likely explanation is that the planner
installs optional bundles. The basic problem is that the publisher (the tool in charge for creating the p2 meta-data)
generates a requirement to install such bundles. This has been fixed but unfortunately the Indigo meta-data is already
out there and cannot be changed. I'm not even sure it will be changed in the next service release. More info here:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=247099
- thomas
|
|
|
| Re: UI artefacts after installing of features into buckminster [message #703224 is a reply to message #703168] |
Wed, 27 July 2011 09:54 |
| Eclipse User |
|
|
|
Originally posted by: Ralf Zozmann
On 07/27/2011 10:11 AM, Thomas Hallgren wrote:
> [...]
> in charge and it wouldn't make the same mistake. A more likely
> explanation is that the planner installs optional bundles. The basic
> problem is that the publisher (the tool in charge for creating the p2
> meta-data) generates a requirement to install such bundles. This has
> been fixed but unfortunately the Indigo meta-data is already out there
> and cannot be changed. I'm not even sure it will be changed in the next
> service release. More info here:
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=247099
>
Hi Thomas,
thanks for that hint. Until now i thought that i can exclude optional
dependencies as reason for the problems, because our old buckminster 3.6
build works in same style. But looking into the installation directory
of that old build reveals also ui artefacts, but without that critical
impact to the build process.
Reading the discussion from
https://bugs.eclipse.org/bugs/show_bug.cgi?id=247099 gives me no
solution. Because i have to suppress the installation of such optional
depdencies (at least for ui bundles).
How can i advice Buckminster to suppress the installation of optional
dependencies (the bundle 'org.eclipse.pde.junit.runtime' seems to be one
with optional dependencies to 'org.eclipse.ui')?
We use a huge composite update site containing references to some local
downloaded content (eclipse mirror etc.) and other external sites, so we
can work with one single update site as source. But in that scenario all
optional bundles are resolvable :-(
Regards
Ralf
|
|
|
| Re: UI artefacts after installing of features into buckminster [message #703343 is a reply to message #703224] |
Wed, 27 July 2011 13:11 |
|
On 2011-07-27 11:54, Ralf Zozmann wrote:
> How can i advice Buckminster to suppress the installation of optional
> dependencies (the bundle 'org.eclipse.pde.junit.runtime' seems to be one
> with optional dependencies to 'org.eclipse.ui')?
You can't unfortunately. Buckminster just delegates the install to the p2 director.
- thomas
|
|
|
| Re: UI artefacts after installing of features into buckminster [message #704216 is a reply to message #703168] |
Thu, 28 July 2011 11:51 |
| Eclipse User |
|
|
|
Originally posted by: Ralf Zozmann
Hi,
currently i'm testing a time-consuming/complex workaround: Download
(mirroring) the required additional features into a local US (without
any dependencies) and install them from there, so all the ui bundles are
suppressed. I have tested two variants:
a) install the feature using the buckminster 'install' command
b) install the feature using the director
The buckminster 'install' fails always with unresolved dependencies
(only from optionals!), but the director can install the feature bundles
without problem.
There seems to be a difference between buckminster and director
processing a feature installation?!
Regards
Ralf
Am 27.07.2011 10:11, schrieb Thomas Hallgren:
> Hi Ralf,
>
> On 2011-07-27 08:55, Ralf Zozmann wrote:
>> Strange! Mmhhh.. is this in any way related to the circular dependency
>> problem of JDT->UI, but in a different bundle (one more patch affecting
>> a normally headless plugin)?
>>
> I don't think it's the same problem since that was related to a
> limitation in Buckminsters resolver. When you install, the p2 planner is
> in charge and it wouldn't make the same mistake. A more likely
> explanation is that the planner installs optional bundles. The basic
> problem is that the publisher (the tool in charge for creating the p2
> meta-data) generates a requirement to install such bundles. This has
> been fixed but unfortunately the Indigo meta-data is already out there
> and cannot be changed. I'm not even sure it will be changed in the next
> service release. More info here:
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=247099
>
> - thomas
|
|
|
| Re: UI artefacts after installing of features into buckminster [message #704580 is a reply to message #704216] |
Thu, 28 July 2011 19:50 |
|
On 2011-07-28 13:51, Ralf Zozmann wrote:
> Hi,
>
> currently i'm testing a time-consuming/complex workaround: Download
> (mirroring) the required additional features into a local US (without
> any dependencies) and install them from there, so all the ui bundles are
> suppressed. I have tested two variants:
> a) install the feature using the buckminster 'install' command
> b) install the feature using the director
>
> The buckminster 'install' fails always with unresolved dependencies
> (only from optionals!), but the director can install the feature bundles
> without problem.
> There seems to be a difference between buckminster and director
> processing a feature installation?!
>
Exactly what commands do you use, and what versions? The Buckminster
install command is only a thin wrapper for the director. It's only
motivation is backward compatibility. What it does is essentially adding
the '.feature.group' suffix to the feature name. When you use the
director you must remember to add that yourself.
- thomas
|
|
|
| Re: UI artefacts after installing of features into buckminster [message #710709 is a reply to message #704580] |
Fri, 05 August 2011 09:59 |
| Eclipse User |
|
|
|
Originally posted by: Ralf Zozmann
Hi Thomas,
i have tested again to give you more informations...
Director version:
org.eclipse.equinox.p2.director.product_1.4.0.v20110505-0000.zip
Buckminster version:
org.eclipse.buckminster.site.eclipse.headless_1.4.0.v20110712-1350.zip
To install features without optional dependencies i have to mirror that
artefacts to a local repository and to install the feature from that
instead from our complete eclipse mirror. To do that i have to install
p2 related bundles for mirroring. So i install the
'org.eclipse.equinox.p2.extras.feature' from the 'equinox-SDK-3.7.zip'
into the buckminster installation. The Director installation i leave
untouched. As result: the unmodified Director may install the feature
org.eclipse.emf.common without problems, the Buckminster will fail.
A Buckminster without additional p2 bundles will also install the
feature without problem.
So the reason for the install problem seems to be the presence of
additional p2 bundles. Looking into the 'equinox-SDK-3.7.zip' i see only
the same versions for bundles also coming with Buckminster.
Regards
Ralf
PS: So i have currently no problem, there is no need to invest more time :-)
Am 28.07.2011 21:50, schrieb Thomas Hallgren:
> On 2011-07-28 13:51, Ralf Zozmann wrote:
>> Hi,
>>
>> currently i'm testing a time-consuming/complex workaround: Download
>> (mirroring) the required additional features into a local US (without
>> any dependencies) and install them from there, so all the ui bundles are
>> suppressed. I have tested two variants:
>> a) install the feature using the buckminster 'install' command
>> b) install the feature using the director
>>
>> The buckminster 'install' fails always with unresolved dependencies
>> (only from optionals!), but the director can install the feature bundles
>> without problem.
>> There seems to be a difference between buckminster and director
>> processing a feature installation?!
>>
> Exactly what commands do you use, and what versions? The Buckminster
> install command is only a thin wrapper for the director. It's only
> motivation is backward compatibility. What it does is essentially adding
> the '.feature.group' suffix to the feature name. When you use the
> director you must remember to add that yourself.
>
> - thomas
|
|
|
| Re: UI artefacts after installing of features into buckminster [message #710723 is a reply to message #710709] |
Fri, 05 August 2011 10:42 |
|
Hi Ralf,
This is interesting. Can you please try to install these extra p2
bundles into the director and see if it has the same negative impact there?
- thomas
On 2011-08-05 11:59, Ralf Zozmann wrote:
> Hi Thomas,
>
> i have tested again to give you more informations...
> Director version:
> org.eclipse.equinox.p2.director.product_1.4.0.v20110505-0000.zip
> Buckminster version:
> org.eclipse.buckminster.site.eclipse.headless_1.4.0.v20110712-1350.zip
>
> To install features without optional dependencies i have to mirror that
> artefacts to a local repository and to install the feature from that
> instead from our complete eclipse mirror. To do that i have to install
> p2 related bundles for mirroring. So i install the
> 'org.eclipse.equinox.p2.extras.feature' from the 'equinox-SDK-3.7.zip'
> into the buckminster installation. The Director installation i leave
> untouched. As result: the unmodified Director may install the feature
> org.eclipse.emf.common without problems, the Buckminster will fail.
> A Buckminster without additional p2 bundles will also install the
> feature without problem.
> So the reason for the install problem seems to be the presence of
> additional p2 bundles. Looking into the 'equinox-SDK-3.7.zip' i see only
> the same versions for bundles also coming with Buckminster.
>
> Regards
> Ralf
> PS: So i have currently no problem, there is no need to invest more time :-)
>
> Am 28.07.2011 21:50, schrieb Thomas Hallgren:
>> On 2011-07-28 13:51, Ralf Zozmann wrote:
>>> Hi,
>>>
>>> currently i'm testing a time-consuming/complex workaround: Download
>>> (mirroring) the required additional features into a local US (without
>>> any dependencies) and install them from there, so all the ui bundles are
>>> suppressed. I have tested two variants:
>>> a) install the feature using the buckminster 'install' command
>>> b) install the feature using the director
>>>
>>> The buckminster 'install' fails always with unresolved dependencies
>>> (only from optionals!), but the director can install the feature bundles
>>> without problem.
>>> There seems to be a difference between buckminster and director
>>> processing a feature installation?!
>>>
>> Exactly what commands do you use, and what versions? The Buckminster
>> install command is only a thin wrapper for the director. It's only
>> motivation is backward compatibility. What it does is essentially adding
>> the '.feature.group' suffix to the feature name. When you use the
>> director you must remember to add that yourself.
>>
>> - thomas
>
|
|
|
| Re: UI artefacts after installing of features into buckminster [message #710841 is a reply to message #710723] |
Fri, 05 August 2011 13:14 |
| Eclipse User |
|
|
|
Originally posted by: Ralf Zozmann
Am 05.08.2011 12:42, schrieb Thomas Hallgren:
> Hi Ralf,
>
> This is interesting. Can you please try to install these extra p2
> bundles into the director and see if it has the same negative impact there?
>
Installing the p2 feature into the director (using the director self)
gives me the follwing output, i think it was successful:
[director] Installing
org.eclipse.equinox.p2.extras.feature.feature.group
1.0.0.v20110519-7A4FD3DiVOManmZvpLOsnBhnPQM3.
[director] Artifact repository out of sync. Overwriting
......\director\plugins\org.eclipse.equinox.security.win32.x86_1.0.200.v20100503.jar
[director] Operation completed in 17047 ms.
Installing the feature org.eclipse.emf.common afterwards using the same
director with additional p2 bundles is simply successfully:
[director] Installing org.eclipse.emf.common.feature.group
2.7.0.v20110605-0747.
[director] Operation completed in 1500 ms.
Regards
Ralf
|
|
|
Powered by
FUDForum. Page generated in 0.03075 seconds
] 
Search
Help
Register
Login
Home
