[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
RE: [orbit-dev] RE: Do we need to provide wrapper featuresforbatik from Orbit?
|
I am concerned about confusion here.
We supply features but they are only template features. furthermore,
features are likely to go away in the new provisioning story so I am loath
to introduce them in new places (yes, I realize that they are here today
and we need to support the scenario you outline). Post-features we
will still need this information so I am thinking that we should just have
the information that is needed and not tie it to features.
Jeff
"Oberhuber, Martin"
<Martin.Oberhuber@xxxxxxxxxxxxx>
Sent by: orbit-dev-bounces@xxxxxxxxxxx
03/22/2007 06:39 AM
Please respond to
Orbit Developer discussion <orbit-dev@xxxxxxxxxxx> |
|
To
| "Orbit Developer discussion"
<orbit-dev@xxxxxxxxxxx>
|
cc
|
|
Subject
| RE: [orbit-dev] RE: Do we need to provide
wrapper featuresforbatik
from Orbit? |
|
Because feature.properties requires
escaping the newlines with a \
at the end of each line, I figured
that it might be simpler copy & pasting
from a feature.properties into
another feature.properties.
That way, the initial provider
of a feature.properties file has no extra
work updating the IP log, and
the consumer who wants to copy
can take an actually working,
verbatim copy.
Cheers,
--
Martin Oberhuber
Wind River Systems, Inc.
Target Management Project Lead, DSDP PMC Member
http://www.eclipse.org/dsdp/tm
From: orbit-dev-bounces@xxxxxxxxxxx
[mailto:orbit-dev-bounces@xxxxxxxxxxx] On Behalf Of Jeff McAffer
Sent: Wednesday, March 21, 2007 11:13 PM
To: Orbit Developer discussion
Subject: Re: [orbit-dev] RE: Do we need to provide wrapper featuresforbatik
from Orbit?
Perhaps we should just include the relevant about text in the IP log. Taht
way people writing a fetaure can just get and include that text as needed....
Amounts to mostly the same thing but perhaps a bit simpler.
Jeff
"Oberhuber, Martin"
<Martin.Oberhuber@xxxxxxxxxxxxx>
Sent by: orbit-dev-bounces@xxxxxxxxxxx
03/21/2007 02:27 AM
Please respond to
Orbit Developer discussion <orbit-dev@xxxxxxxxxxx> |
|
To
| "Cross project issues"
<cross-project-issues-dev@xxxxxxxxxxx>, "Orbit Developer discussion"
<orbit-dev@xxxxxxxxxxx>
|
cc
|
|
Subject
| [orbit-dev] RE: Do we need to provide
wrapper featuresfor batik from 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
_______________________________________________
orbit-dev mailing list
orbit-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/orbit-dev
_______________________________________________
orbit-dev mailing list
orbit-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/orbit-dev