|
|
|
|
| Re: Buckminster headless product has a version conflict with Eclipse 3.8.2 and 4.2.2 [message #1033715 is a reply to message #1033697] |
Thu, 04 April 2013 14:57   |
|
On 2013-04-04 16:33, Tobias Bertelsen wrote:
> Thomas Hallgren wrote on Thu, 04 April 2013 15:33
>> On 2013-04-04 14:37, In that case you're doing something wrong. You
>> should not attempt to install the Buckminster product into another
>> product. Install the features that you need instead.
>
>
> Let's say I needed the org.eclipse.buckminster.installer bundle. This
> has no dependencies, but it is included in two features,
> org.eclipse.buckminster.core.feature and
> org.eclipse.buckminster.product. The core feature contains a lot of UI
> plugins, so if I don't want those I'm left with the product feature.
>
The product contains headless features that indeed does conflict with
the IDE product. This is intentional. The features are named headless to
emphasize the fact that they are not intended to be installed into the IDE.
Why do you want to avoid the Buckminster UI feature when you're
installing into Eclipse?
> A workarround to get org.eclipse.buckminster.cmdline and
> org.eclipse.buckminster.runtime is to just install
> org.eclipse.buckminster.core.headless.feature. This will drag them in as
> dependencies. You can't get the installer this way, as nothing depends
> on it.
>
The installer is just a thin layer on top of the director. It was
created before the director existed and then kept around for backward
compatibility. The director provides all the functionality so you don't
really need the installer.
>
> Yet another way to solve this is to change the structure of the product
> feature. Let's say you divided the product into two features:
> Buckminster-essentials and Eclipse-essentials (see below). In this case
> users like me, could choose only to import the Buckminster essentials.
>
The former doesn't sound like a product feature to me. A product defines
a root (with binaries etc.). Installing a product into another product
is bound to produce conflicts.
- thomas
|
|
|
| Re: Buckminster headless product has a version conflict with Eclipse 3.8.2 and 4.2.2 [message #1033719 is a reply to message #1033666] |
Thu, 04 April 2013 15:04 |
|
On 2013-04-04 15:48, Peter Nehrer wrote:
> I'm running into the same problem when trying to include Buckminster
> Headless in my target platform (via p2) with Eclipse SDK.
>
Why not just include the core headless core feature then? If you have
the SDK in there, then surely you don't need the Buckminster product.
> Thomas, are there any plans to change how Headless is packaged? Maybe it
> could pull in Platform dependencies instead of including them.
But we already do that! Not for the product mind you, but well for the
features.
Again, a product is not meant to be installed into other types of
constellations. Please use the features instead. That's why we have
them. If you feel that some type of feature is missing, then we can
discuss that. The headless product will however not change in this respect.
- thomas
|
|
|
| Re: Buckminster headless product has a version conflict with Eclipse 3.8.2 and 4.2.2 [message #1033735 is a reply to message #1033719] |
Thu, 04 April 2013 15:24 |
 Peter Nehrer
Messages: 241
Registered: July 2009 |
Senior Member |
|
|
I see, thank you for the pointers -- I have to take another look at this.
Essentially what I tried to do at some point was to create a top-level
product (custom) that includes all Buckminster features that I wanted in
that root IU. For that I had to pull everything into my target platform
(and I had other things in it) and that's where I ran into trouble.
I wish there was a way to mirror-in existing features from an external
p2 repository instead of pulling them into the target platform (and
losing all kinds of metadata in the process). Maybe b3 does that?
Haven't looked.
I ended up just requiring all those features so they do get installed in
the end, but that's not exactly the same thing.
Anyway I see your point, I'll take another look. Thanks.
On 4/4/13 11:04 AM, Thomas Hallgren wrote:
> On 2013-04-04 15:48, Peter Nehrer wrote:
>> I'm running into the same problem when trying to include Buckminster
>> Headless in my target platform (via p2) with Eclipse SDK.
>>
> Why not just include the core headless core feature then? If you have
> the SDK in there, then surely you don't need the Buckminster product.
>
>> Thomas, are there any plans to change how Headless is packaged? Maybe it
>> could pull in Platform dependencies instead of including them.
>
> But we already do that! Not for the product mind you, but well for the
> features.
>
> Again, a product is not meant to be installed into other types of
> constellations. Please use the features instead. That's why we have
> them. If you feel that some type of feature is missing, then we can
> discuss that. The headless product will however not change in this respect.
>
> - thomas
>
|
|
|
Powered by
FUDForum. Page generated in 0.04134 seconds
] 
Search
Help
Register
Login
Home
