|
| Re: Is it now time to convert plugins to OSGI? [message #42997 is a reply to message #42780] |
Fri, 04 June 2004 20:38   |
Eclipse User |
|
|
|
Originally posted by: chaves.nospam.inf.ufsc.br
All plugins in Eclipse 3.0 end up having manifest.mf files. For those who
don't provide one, a new manifest.mf will be automatically generated based
on the plugin.xml/fragment.xml files and the contents of the plugin JAR
files.
If you find any problems in the doc you mentioned or in the OSGi-related
behavior, feel free to open bugs against Equinox/General to report the
issue.
Rafael
Michael Scharf wrote:
> Hi,
> we are in the process or migrating our 2.x plugins to 3.0.
> Is it now time to switch to OSGI?
> It seems eclipse itself is not really using OSGI (only SWT and ide.build
> use MANIFEST files (+the osgi itself)).
> Is this an indication that it is not ready for "prime time"?
> Is this information up to date?
>
http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform -core-home/runtime/adoption.html
> Michael
|
|
|
| Re: Is it now time to convert plugins to OSGI? [message #43079 is a reply to message #42780] |
Wed, 09 June 2004 00:15 |
| Eclipse User |
|
|
|
Originally posted by: pascal.ibm.canada
OSGi is ready for prime time, however the tooling does not support all
the things that the runtime supports but what is provided now is already
solid.
For more details see my answer to the message "osgi or no".
PaScaL
Michael Scharf wrote:
> Hi,
>
> we are in the process or migrating our 2.x plugins to 3.0.
> Is it now time to switch to OSGI?
> It seems eclipse itself is not really using OSGI (only SWT and ide.build
> use MANIFEST files (+the osgi itself)).
> Is this an indication that it is not ready for "prime time"?
>
> Is this information up to date?
>
> http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform -core-home/runtime/adoption.html
>
>
> Michael
|
|
|
Powered by
FUDForum. Page generated in 0.02430 seconds
] 
Search
Help
Register
Login
Home
