Eclipse Community Forums: Buckminster » The way fragments are treated

Home » Archived » Buckminster » The way fragments are treated

The way fragments are treated [message #541974]

Wed, 23 June 2010 08:29

Eclipse User

I am using the Babel project in my RCP app.

The Babel project has features for each language. For example,
org.eclipse.babel.nls_eclipse_de is the feature for the German Babel
project.

Unfortunately (for me) this feature includes language translations (in the
form of a plugin fragment) for every plugin in Eclipse.

I have included this feature in my "external features" feature, and I am now
getting errors related to Buckminster not being able to find components in
the Eclipse repository:

E.g

ERROR [0000] : No suitable provider for component
org.eclipse.ltk.ui.refactoring.tests:osgi.bundle was found in searchPath
org.eclipse.platform
ERROR [0000] : Rejecting provider
p2( http://download.eclipse.org/releases/galileo?importType=bina ry): No
component match was found

I noticed two things from this:
*Most of the errors are related to plugin fragments for unit test plugins
(which I assume are not available from the download.eclipse.org repo.
*All of the errors are related to fragments

Questions:

Is Buckminster trying to pull down the host bundle?

And the big one:

Can I tell Buckminster to ignore fragments without an existing host?

Failing that, what is the best way to solve this?

Should I just create my own Babel feature including only the Babel features
that I need and that have host plugins at the download.eclipse.org repo?

Thanks again for the past excellent, quick help

Greg

Re: The way fragments are treated [message #541999 is a reply to message #541974]

Wed, 23 June 2010 09:40

Eclipse User

On 06/23/2010 02:29 PM, geejay wrote:
> Questions:
>
> Is Buckminster trying to pull down the host bundle?
>
That's likely yes, since the fragment has a requirement to its host.

> And the big one:
>
> Can I tell Buckminster to ignore fragments without an existing host?
>
You can tell Buckminster to completely skip some components (regardless of type) by adding an advisor node to the cquery
with a name pattern that matches the component(s) that you don't want and then check the 'Skip this component' in that node.

HTH,
- thomas

Previous Topic:	Convert target platform to p2 update site
Next Topic:	site.p2 for product configuration always creates and includes source feature

Goto Forum:

-=] Back to Top [=-

Current Time: Mon Jun 09 17:24:26 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter