Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Buckminster » No component named org.eclipse.equinox.launcher.motif.hpux.PA_RISC
No component named org.eclipse.equinox.launcher.motif.hpux.PA_RISC [message #545152] Tue, 06 July 2010 15:17 Go to next message
Stephan  is currently offline Stephan
Messages: 36
Registered: July 2009
Member
Hi

I have just installed Eclipse 3.6 with the Delta Pack and Buckminster Core and PDE Support. Then I tried to do a Buckminster build (site.p2) inside Eclipse but get the following error:
No component named org.eclipse.equinox.launcher.motif.hpux.PA_RISC:osgi.bundle/ [1.0.0,raw:MpM)(&(target.arch=PA_RISC)(target.os=hpux)(t arget.ws=motif)) is known to Buckminster

I checked the DeltaPack and *motif.hpux.PA_RISC is really not included anymore (it was in 3.5.1). Is this support removed by design?

I don't really care about motif.hpux.PA_RISC but I build my site with:
target.os=*
target.ws=*
target.arch=*

Is there a ways to set a filter to build all target.arch except PA_RISC?

Thanks, Stephan
Re: No component named org.eclipse.equinox.launcher.motif.hpux.PA_RISC [message #545197 is a reply to message #545152] Wed, 07 July 2010 02:40 Go to previous messageGo to next message
Thomas Hallgren is currently offline Thomas Hallgren
Messages: 3214
Registered: July 2009
Senior Member
Hi Stephan,

What component is it that requires the PA_RISC launcher? It is not listed in the org.eclipse.equinox.executable feature
so I can't see why Buckminster should try and resolve it.

- thomas


On 07/06/2010 09:17 PM, Stephan wrote:
> Hi
>
> I have just installed Eclipse 3.6 with the Delta Pack and Buckminster
> Core and PDE Support. Then I tried to do a Buckminster build (site.p2)
> inside Eclipse but get the following error:
> No component named
> org.eclipse.equinox.launcher.motif.hpux.PA_RISC:osgi.bundle/
> [1.0.0,raw:MpM)(&(target.arch=PA_RISC)(target.os=hpux)(t
> arget.ws=motif)) is known to Buckminster
>
> I checked the DeltaPack and *motif.hpux.PA_RISC is really not included
> anymore (it was in 3.5.1). Is this support removed by design?
>
> I don't really care about motif.hpux.PA_RISC but I build my site with:
> target.os=*
> target.ws=*
> target.arch=*
>
> Is there a ways to set a filter to build all target.arch except PA_RISC?
>
> Thanks, Stephan
>
Re: No component named org.eclipse.equinox.launcher.motif.hpux.PA_RISC [message #545584 is a reply to message #545197] Thu, 08 July 2010 06:28 Go to previous messageGo to next message
Stephan  is currently offline Stephan
Messages: 36
Registered: July 2009
Member
Hi Thomas

Sorry, this was my fault. We created a (reduced) copy of org.eclipse.rcp for our "rich server applications" and there PA_RISC was still referenced. Now I deleted the launcher* plugins from our server feature and include the feature org.eclipse.equinox.executable instead. After this change the build worked fine again.

Questions:
a) In the Buckminster book, the product example references org.eclipse.rcp and org.eclipse.equinox.executable. Is the later really needed because the same references are already part of o.e.rcp?
b) Any ideas why o.e.rcp does not include o.e.e.executable?

Cheers, Stephan
Re: No component named org.eclipse.equinox.launcher.motif.hpux.PA_RISC [message #545846 is a reply to message #545584] Fri, 09 July 2010 07:37 Go to previous message
Thomas Hallgren is currently offline Thomas Hallgren
Messages: 3214
Registered: July 2009
Senior Member
Hi Stephan,

On 07/08/2010 12:28 PM, Stephan wrote:
> Hi Thomas
>
> Sorry, this was my fault. We created a (reduced) copy of org.eclipse.rcp
> for our "rich server applications" and there PA_RISC was still
> referenced. Now I deleted the launcher* plugins from our server feature
> and include the feature org.eclipse.equinox.executable instead. After
> this change the build worked fine again.
>
> Questions:
> a) In the Buckminster book, the product example references
> org.eclipse.rcp and org.eclipse.equinox.executable. Is the later really
> needed because the same references are already part of o.e.rcp?

If you're using the o.e.rcp then you don't need the o.e.e.executable. It is only needed when you want to build things
that doesn't include a UI and hence cannot use o.e.rcp.

> b) Any ideas why o.e.rcp does not include o.e.e.executable?
>

I think the reason is that historically the o.e.e.executable is considered a "build time" feature. This has since been
fixed:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=264743#c6

The feature still contains references to launchers that doesn't exist. I raised a bug for this earlier today:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=319345

All in all, I consider the whole "delta pack" business a bit ugly. It can (and IMHO should) be replaced by proper
resolution using p2 repositories. Buckminsters own builds stopped using the delta pack as soon as p2 entered the scene
and the o.e.e.executable became available.

Regards,
Thomas Hallgren
Previous Topic:PDE Junit Tests with Buckminster for a simple RCP
Next Topic:p2.site of a feature contains wrong plugin versions
Goto Forum:
  


Current Time: Wed Jul 30 01:14:51 EDT 2014

Powered by FUDForum. Page generated in 0.03040 seconds