Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [cross-project-issues-dev] Orbit enablement features?

This is a common pitfall -- your releng build process needs
to use the Eclipse Packager, in order to pick up the bundles
retrieved through GET in the map.

Not sure if this is mentioned in the Orbit HOWTO already?

Cheers,
--
Martin Oberhuber
Wind River Systems, Inc.
Target Management Project Lead, DSDP PMC Member
http://www.eclipse.org/dsdp/tm 

> -----Original Message-----
> From: cross-project-issues-dev-bounces@xxxxxxxxxxx 
> [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On 
> Behalf Of Marcin Okraszewski
> Sent: Tuesday, April 17, 2007 3:26 PM
> To: Cross project issues
> Subject: Re: [cross-project-issues-dev] Orbit enablement features?
> 
> I'm getting a bit confused. If I'm correct my distribution should 
> contain the required libraries from the Orbit. But it seems 
> we shouldn't 
> build it for our own, because the "qualifier" will be 
> replaced with our 
> build ID. This may result in several instances of the same 
> library. This 
> is what we want to avoid I think. So we updated our maps to use the 
> pre-built plugins from Orbit over HTTP. The plugins are downloaded, 
> build succeeds. But the build result doesn't contain the 
> Orbit plugins.
> 
> Am I missing something?
> 
> Regards,
> Marcin
> 
> 
> Richard Gronback wrote:
> > You may want to follow this:
> > https://bugs.eclipse.org/bugs/show_bug.cgi?id=171955
> >
> > Best,
> > Rich
> >
> >
> > On 4/17/07 6:17 AM, "Marcin Okraszewski"
> > <marcin.okraszewski@xxxxxxxxxxxxxxxx> wrote:
> >
> >   
> >> I wonder if Orbit should provide its features to Europa 
> update site? It
> >> is somehow confusing, since there are several third party library
> >> features in "Enabling Features".  But they are delivered by several
> >> projects (eg. WTP). So, we cannot relay that it will 
> always be there,
> >> since for instance WTP may change version of the library 
> they use. This
> >> means that still every project needs to include Orbit 
> plugins for its
> >> own - and I think it is suggested at Orbit pages.
> >>
> >> So if Corona uses Xerces and WTP uses Xerces, should we 
> include it in
> >> our "base" feature, or create one in "Enabling Features"? 
> It would be
> >> strange to have two Xerces features - one by WTP one from Corona.
> >> Wouldn't it be best if Orbit exposes all its libraries as 
> enabling features?
> >>
> >> Ragards,
> >> Marcin Okraszewski
> >> The contents of this e-mail are intended for the named 
> addressee only. It
> >> contains information that may be confidential. Unless you 
> are the named
> >> addressee or an authorized designee, you may not copy or 
> use it, or disclose
> >> it to anyone else. If you received it in error please 
> notify us immediately
> >> and then destroy it.
> >> _______________________________________________
> >> cross-project-issues-dev mailing list
> >> cross-project-issues-dev@xxxxxxxxxxx
> >> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
> >>     
> >
> >   
> The contents of this e-mail are intended for the named 
> addressee only. It contains information that may be 
> confidential. Unless you are the named addressee or an 
> authorized designee, you may not copy or use it, or disclose 
> it to anyone else. If you received it in error please notify 
> us immediately and then destroy it. 
> _______________________________________________
> cross-project-issues-dev mailing list
> cross-project-issues-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
> 


Back to the top