Jeff McAffer wrote:
plugin == bundle. In 3.1 all Eclipse plugins have normal MANIFEST.MF
files etc. and so are just normal bundles. Some of these bundles MAY
happen to have additional files such as plugin.xml that are meant for
Eclipse-specific services but this is no different than say the structure
of the OSGi declarative services mechanism.
I see, every Eclipse plugin is an OSGi-compliant bundle.
But my point was that Eclipse does not have certain services that are
mandatory in the OSGi spec, so I can not deploy any OSGi-compliant
bundle to Eclipse, correct?
Note also that your list of scenarios does not include server-side. The
Eclipse OSGi implementation (as I'm sure others) is being used on the
server as well.
Thanks for the pointer. I have to admit that I am not familiar with this
application area, will take this offline.
Jeff
Tom <[EMAIL PROTECTED]>
08/04/2005 05:42 PM
Please respond to
oscar-dev
To
[email protected]
cc
Subject
Re: Oscar, please meet Eclipse
Thanks for your clarification, corrected my list:
http://www.gatewide.com/tenderes_html/projects/osgi_appreqs.txt
(Just to make sure I understand correctly: eRPC is still the core
framework only, e.g. I can deploy an "embedded plugin" via eUpdate to an
eRCP device, but I can not deploy an OSGi bundle, right?)
Mike Milinkovich wrote:
I think that there is one misunderstanding which needs to be corrected.
The
Eclipse OSGi runtime is being used in more places than the IDE and
workstation. A specific example is the eRCP project
(www.eclipse.org/ercp)
which is supporting Nokia Series 80 and Windows Mobile 2003.
-----Original Message-----
Requirements according to application area:
-------------------------------------------
Eclipse Applications (IDE, Rich client):
- Software goals: Code Quality & Stability, Scalability to
many different bundles, startup/load times...
- Installation & Deployment: Eclipse Runtime
- Legal: Eclipes License code only?
