|
| Re: core.runtime vs. equinox.common [message #905392 is a reply to message #903910] |
Thu, 30 August 2012 09:54  |
|
Hi Ralf,
bundle symbolic name doesn't have to match to its Java packages (both
exported and private). E.g. full content of Java package
org.eclipse.core.runtime is actually spread into other bundles, most
notably, org.eclipse.equinox.common and org.eclipse.equinox.registry.
Bundle org.eclipse.core.runtime itself requires others bundles
contributing content of org.eclipse.core.runtime Java package, reexports
this dependencies and therefore ease client usage (you can depend just
on this plug-in and receive everything needed in single step).
See more at
http://help.eclipse.org/juno/topic/org.eclipse.platform.doc.isv/reference/misc/overview-platform.html?cp=2_1_3_5.
Libor
http://devblog.virtage.com/tag/eclipse/
On 08/27/2012 10:40 AM, Ralf Sternberg wrote:
> Hi,
>
> I'm trying to understand the role of the bundles core.runtime and
> equinox.common. Reading the doc on runtime components [1], it seems that
> the core.runtime bundle would be superseded by equinox.common and should
> not be used anymore by new applications - is this true?
>
> Since equinox.common basically exports the core.runtime package,
> shouldn't it have a name in the eclipse.core space?
>
> Are there any future plans regarding these bundles?
>
> Thanks,
> Ralf
>
>
> [1]
> http://help.eclipse.org/juno/index.jsp?topic=%2Forg.eclipse.platform.doc.isv%2Fguide%2Fruntime_components.htm
>
|
|
|
Powered by
FUDForum. Page generated in 0.02866 seconds
] 
Search
Help
Register
Login
Home
