[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [equinox-dev] Transition


Good point.  Do you have some examples?  Keep in mind that the "services" component is targetted at implementations of the other parts of the spec, not random other function.  How does the full OSGi itself talk about the distinction between the core framework and these other parts?

Jeff



BJ Hargrave <hargrave@xxxxxxxxxx>
Sent by: equinox-dev-bounces@xxxxxxxxxxx

09/05/2005 09:51 AM

Please respond to
Equinox development mailing list

To
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
cc
Subject
Re: [equinox-dev] Transition





I like it.

Perhaps the organization should be framework/*bundles*/incubator. There
are many interesting bundles which do not themselves provide services. So
calling the component bundles rather than services is more general.

BJ Hargrave
Senior Software Engineer, IBM
OSGi Fellow and CTO of the OSGi Alliance
hargrave@xxxxxxxxxx
Office: +1 407 849 9117 Mobile: +1 386 848 3788



Jeff McAffer <Jeff_McAffer@xxxxxxxxxx>
Sent by: equinox-dev-bounces@xxxxxxxxxxx
2005-09-03 10:32 PM
Please respond to
Equinox development mailing list


To
equinox-dev@xxxxxxxxxxx
cc

Subject
[equinox-dev] Transition







There is a move afoot to transition Equinox to the Eclipse PMC and develop
it into an OSGi community.  Please take a minute to review the
documentation at
       
http://dev.eclipse.org/viewcvs/indextech.cgi/~checkout~/equinox-home/transition.html

and surface any issues or questions.  

Jeff _______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev


_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev