Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[cross-project-issues-dev] RE: [orbit-dev] RE: Do we need to provide wrapper featuresfor batikfrom Orbit?

Thanks for your help!

That means we need to add the Orbit bundles to “Include Plugins”  in our own features (e.g. org.eclipse.birt.feature).

 

I thought we are expected to copy Orbit bundles directly into our build environment but not check out from Orbit CVS, are we?

According to the BaseBuilder mechanism, it performs “checkout-generate script-build” steps. I’m confused how PDE basebuilder build these features (e.g. org.eclipse.birt.feature), as we don’t list them in the map file.  It might be a pde-build question rather than an Orbit questionJ

Could anyone give me any suggestion? Thanks!

 

Xiaoying

 


From: orbit-dev-bounces@xxxxxxxxxxx [mailto:orbit-dev-bounces@xxxxxxxxxxx] On Behalf Of Oberhuber, Martin
Sent: Wednesday, March 21, 2007 5:27 PM
To: Cross project issues; Orbit Developer discussion
Subject: [orbit-dev] RE: Do we need to provide wrapper featuresfor batikfrom Orbit?

 

Hello Xiaojing,

 

Orbit practice is that every product/download which wants to use

bundles from Orbit just includes those Orbit bundles in its features.

 

There is no "wrapper feature" for a single Orbit delivery any more.

 

In terms of the license text for your features, you will need to include

references to the licenses under which your Orbit bundles are,

in your own feature.properties. Since potentially multiple projects

need to do that for multiple features, it might be a good idea to

maintain these in a central location or at least maintain a pointer

to where a sample feature.properties is.

 

This might be another application for the IP Log that's currently

being discussed in Orbit: See

http://wiki.eclipse.org/index.php/Orbit_IP_Log

 

I added this comment: I think we should also have a "used-by"

section listing all the projects at Eclipse.org which are known

to actually use a bundle/version (i.e. include it in one of their features).

A hyperlink into ViewVC for the CVS/SVN version of the feature

project would perhaps be most helpful. This would not only track

usage, but also help other projects who want to adopt it get started

with their own feature.xml / feature.properties. When I'm not mistaken,

from a legal standpoint every project needs to put an Orbit bundle

it wants to pick up through review for usage in their project, so it seems

natural to maintain the list of known users.

 

As long as this is not yet in place, the maintainer of an Orbit

bundle is the first address to ask for a good feature.xml / feature.properties

example, since it is very likely that this maintainer uses the bundle

in his or her own project.

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

 

 


From: cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of Xiaoying Gu
Sent: Wednesday, March 21, 2007 6:08 AM
To: Cross project issues; orbit-dev-request@xxxxxxxxxxx
Subject: [cross-project-issues-dev] Do we need to provide wrapper featuresfor batik from Orbit?

Hi

 

We are switching to use batik from Orbit.

Since Orbit download doesn’t provider “wrapper” features, does every project need to provide “wrapper” features (e.g. org.apache.batik.feature) themselves? If so, I’m confused how to make these features have consistent features versions?

If no wrapper features are expected to provide by each project themselves in Europa, does that mean users will need to download Orbit project from website or install from Europa Update Site first?

 

Thanks,

Xiaoying Gu

 


Back to the top