Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Runtimes » Extend the runtime project scope
Extend the runtime project scope [message #468616] Fri, 30 May 2008 06:36 Go to next message
Markus Kuppe is currently offline Markus KuppeFriend
Messages: 177
Registered: July 2009
Senior Member
Hi,

currently the runtime (rt) project draft charter [1] lists a) as one of
its project scopes. I propose to change it into b), to show potential
adopters that rt projects make OSGi interoperability [2] one of their
key features.
In practise I'd expect rt projects to at least continuously test their
bundles not just with Equinox, but other R4 implementations.

Regards
Markus

a) "All implementations must be based on OSGi and run on Equinox."
b) "All implementations must be based and run on any R4 compliant OSGi
implementation".

[1] http://wiki.eclipse.org/Runtime_Top-Level_Project_Draft_Char ter#Scope
[2] http://www.osgi.org/About/Technology
Re: Extend the runtime project scope [message #468618 is a reply to message #468616] Thu, 12 June 2008 19:06 Go to previous messageGo to next message
Jeff McAffer is currently offline Jeff McAfferFriend
Messages: 104
Registered: July 2009
Senior Member
Markus,

That certainly is a good goal however Equinox offers many extensions
that are required in real runtime scenarios. Saying that all RT project
output has to run on any R4 framework would limit our ability to exploit
those facilities.

Jeff

Markus Alexander Kuppe wrote:
> Hi,
>
> currently the runtime (rt) project draft charter [1] lists a) as one of
> its project scopes. I propose to change it into b), to show potential
> adopters that rt projects make OSGi interoperability [2] one of their
> key features.
> In practise I'd expect rt projects to at least continuously test their
> bundles not just with Equinox, but other R4 implementations.
>
> Regards
> Markus
>
> a) "All implementations must be based on OSGi and run on Equinox."
> b) "All implementations must be based and run on any R4 compliant OSGi
> implementation".
>
> [1] http://wiki.eclipse.org/Runtime_Top-Level_Project_Draft_Char ter#Scope
> [2] http://www.osgi.org/About/Technology
Re: Extend the runtime project scope [message #468620 is a reply to message #468618] Mon, 16 June 2008 13:12 Go to previous messageGo to next message
Markus Kuppe is currently offline Markus KuppeFriend
Messages: 177
Registered: July 2009
Senior Member
Jeff McAffer wrote:
> Markus,
>
> That certainly is a good goal however Equinox offers many extensions
> that are required in real runtime scenarios. Saying that all RT project
> output has to run on any R4 framework would limit our ability to exploit
> those facilities.
>
> Jeff

Jeff,

that pretty much sounds like the OSGi R4 spec doesn't life up to real
runtime scenarios/requirements. I'm not sure this is the case, though I
won't argue that it is desirable to exploit the full functionality of
Equinox.
Correct me if I'm wrong, but I question that the majority of bundles
need to use non spec compliant features in order to be usable in real
runtime scenarios.

Markus
Re: Extend the runtime project scope [message #468622 is a reply to message #468620] Thu, 19 June 2008 10:44 Go to previous messageGo to next message
Christian Campo is currently offline Christian CampoFriend
Messages: 590
Registered: July 2009
Senior Member
Markus,

are you saying that projects in RT are required to run against other R4 implementations. What if projects in RT does not
have that requirment. Cant they live in that space anymore ?

I think nothing stops a project to commit to go beyond the requirements of the top level project. But thats not
necessarily true for all projects.

What about Extensions that are in the Equinox SDK but probably not in a Felix SDK I assume ? I know they would run there
but they are not part of the R4 spec as I recall. So is using Extensions as the Workbench does all over the place a
forbidden thing then for a RT project ?

just my 2 cent

christian


Markus Alexander Kuppe schrieb:
> Jeff McAffer wrote:
>> Markus,
>>
>> That certainly is a good goal however Equinox offers many extensions
>> that are required in real runtime scenarios. Saying that all RT
>> project output has to run on any R4 framework would limit our ability
>> to exploit those facilities.
>>
>> Jeff
>
> Jeff,
>
> that pretty much sounds like the OSGi R4 spec doesn't life up to real
> runtime scenarios/requirements. I'm not sure this is the case, though I
> won't argue that it is desirable to exploit the full functionality of
> Equinox.
> Correct me if I'm wrong, but I question that the majority of bundles
> need to use non spec compliant features in order to be usable in real
> runtime scenarios.
>
> Markus
Re: Extend the runtime project scope [message #468624 is a reply to message #468622] Mon, 23 June 2008 05:55 Go to previous message
Markus Kuppe is currently offline Markus KuppeFriend
Messages: 177
Registered: July 2009
Senior Member
Christian Campo wrote:
> Markus,
>
> are you saying that projects in RT are required to run against other R4
> implementations. What if projects in RT does not have that requirment.
> Cant they live in that space anymore ?
>
> I think nothing stops a project to commit to go beyond the requirements
> of the top level project. But thats not necessarily true for all projects.
>
> What about Extensions that are in the Equinox SDK but probably not in a
> Felix SDK I assume ? I know they would run there but they are not part
> of the R4 spec as I recall. So is using Extensions as the Workbench does
> all over the place a forbidden thing then for a RT project ?
>
> just my 2 cent
>
> christian

Christian,

IMO we should require projects who live in rt to be R4 compatible with a
"lightweight" process to make an exception on a per bundle basis.
In general I don't want to drive projects out of rt, but to reach the
consent that interoperability is a major goal of rt.

Markus
Re: Extend the runtime project scope [message #571938 is a reply to message #468616] Thu, 12 June 2008 19:06 Go to previous message
Jeff McAffer is currently offline Jeff McAfferFriend
Messages: 104
Registered: July 2009
Senior Member
Markus,

That certainly is a good goal however Equinox offers many extensions
that are required in real runtime scenarios. Saying that all RT project
output has to run on any R4 framework would limit our ability to exploit
those facilities.

Jeff

Markus Alexander Kuppe wrote:
> Hi,
>
> currently the runtime (rt) project draft charter [1] lists a) as one of
> its project scopes. I propose to change it into b), to show potential
> adopters that rt projects make OSGi interoperability [2] one of their
> key features.
> In practise I'd expect rt projects to at least continuously test their
> bundles not just with Equinox, but other R4 implementations.
>
> Regards
> Markus
>
> a) "All implementations must be based on OSGi and run on Equinox."
> b) "All implementations must be based and run on any R4 compliant OSGi
> implementation".
>
> [1] http://wiki.eclipse.org/Runtime_Top-Level_Project_Draft_Char ter#Scope
> [2] http://www.osgi.org/About/Technology
Re: Extend the runtime project scope [message #571999 is a reply to message #468618] Mon, 16 June 2008 13:12 Go to previous message
Markus Kuppe is currently offline Markus KuppeFriend
Messages: 177
Registered: July 2009
Senior Member
Jeff McAffer wrote:
> Markus,
>
> That certainly is a good goal however Equinox offers many extensions
> that are required in real runtime scenarios. Saying that all RT project
> output has to run on any R4 framework would limit our ability to exploit
> those facilities.
>
> Jeff

Jeff,

that pretty much sounds like the OSGi R4 spec doesn't life up to real
runtime scenarios/requirements. I'm not sure this is the case, though I
won't argue that it is desirable to exploit the full functionality of
Equinox.
Correct me if I'm wrong, but I question that the majority of bundles
need to use non spec compliant features in order to be usable in real
runtime scenarios.

Markus
Re: Extend the runtime project scope [message #572029 is a reply to message #468620] Thu, 19 June 2008 10:44 Go to previous message
Christian Campo is currently offline Christian CampoFriend
Messages: 590
Registered: July 2009
Senior Member
Markus,

are you saying that projects in RT are required to run against other R4 implementations. What if projects in RT does not
have that requirment. Cant they live in that space anymore ?

I think nothing stops a project to commit to go beyond the requirements of the top level project. But thats not
necessarily true for all projects.

What about Extensions that are in the Equinox SDK but probably not in a Felix SDK I assume ? I know they would run there
but they are not part of the R4 spec as I recall. So is using Extensions as the Workbench does all over the place a
forbidden thing then for a RT project ?

just my 2 cent

christian


Markus Alexander Kuppe schrieb:
> Jeff McAffer wrote:
>> Markus,
>>
>> That certainly is a good goal however Equinox offers many extensions
>> that are required in real runtime scenarios. Saying that all RT
>> project output has to run on any R4 framework would limit our ability
>> to exploit those facilities.
>>
>> Jeff
>
> Jeff,
>
> that pretty much sounds like the OSGi R4 spec doesn't life up to real
> runtime scenarios/requirements. I'm not sure this is the case, though I
> won't argue that it is desirable to exploit the full functionality of
> Equinox.
> Correct me if I'm wrong, but I question that the majority of bundles
> need to use non spec compliant features in order to be usable in real
> runtime scenarios.
>
> Markus
Re: Extend the runtime project scope [message #572076 is a reply to message #468622] Mon, 23 June 2008 05:55 Go to previous message
Markus Kuppe is currently offline Markus KuppeFriend
Messages: 177
Registered: July 2009
Senior Member
Christian Campo wrote:
> Markus,
>
> are you saying that projects in RT are required to run against other R4
> implementations. What if projects in RT does not have that requirment.
> Cant they live in that space anymore ?
>
> I think nothing stops a project to commit to go beyond the requirements
> of the top level project. But thats not necessarily true for all projects.
>
> What about Extensions that are in the Equinox SDK but probably not in a
> Felix SDK I assume ? I know they would run there but they are not part
> of the R4 spec as I recall. So is using Extensions as the Workbench does
> all over the place a forbidden thing then for a RT project ?
>
> just my 2 cent
>
> christian

Christian,

IMO we should require projects who live in rt to be R4 compatible with a
"lightweight" process to make an exception on a per bundle basis.
In general I don't want to drive projects out of rt, but to reach the
consent that interoperability is a major goal of rt.

Markus
Previous Topic:Extend the runtime project scope
Next Topic:Website incomplete
Goto Forum:
  


Current Time: Sat Dec 20 20:12:50 GMT 2014

Powered by FUDForum. Page generated in 0.10211 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software