| org.eclipse.core.runtime.CoreException [message #181769] |
Mon, 27 November 2006 03:55  |
Eclipse User |
|
|
|
Originally posted by: ybelov.yahoo.com
This class was packaged inside the org.eclipse.core.runtime_3.1.2.jar for
eclipse 3.1; in the eclipse 3.2 however it seems to be missing (or I am
blind). CoreException is used by org.eclipse.ui.plugin.AbstractUIPlugin
class.
Does anyone know what happened to org.eclipse.core.runtime.CoreException
in 3.2?
Do I use a different class to AbstractUIPlugin?
|
|
|
|
|
| Re: org.eclipse.core.runtime.CoreException [message #181889 is a reply to message #181881] |
Mon, 27 November 2006 23:28  |
| Eclipse User |
|
|
|
Originally posted by: wharley.bea.com
"Yakov" <ybelov@yahoo.com> wrote in message
news:f1e8bd4a4793481059d4e61a7743e8ee$1@www.eclipse.org...
> Remy Suen wrote:
>> CoreException is in org.eclipse.equinox.common now.
>
>> Regards,
>> Rem
> Thank you, Remy! Just out of interest, why such a choice of packaging?
Equinox is an effort to provide a standalone OSGi implementation, in part by
refactoring OSGi code that used to be in the Platform project into a
separate project. In other words, Eclipse's OSGi implementation used to
just be mixed in with the rest of Platform; Equinox separates it into its
own project, for clarity and for the benefit of users who need just an OSGi
implementation without the rest of Platform.
As a result, many classes that used to be in org.eclipse.core.* plug-ins
were moved to org.eclipse.equinox.* plug-ins. But the classes themselves
are API so the package names can't easily be changed, and in fact those
classes are re-exported from the old plug-ins via entries in the old plug-in
manifests. For instance, org.eclipse.core.runtime imports
org.eclipse.equinox.common and re-exports its contents.
You can learn more by following the "Equinox" link from
http://www.eclipse.org/eclipse/.
|
|
|
| Re: org.eclipse.core.runtime.CoreException [message #181895 is a reply to message #181889] |
Tue, 28 November 2006 02:19 |
| Eclipse User |
|
|
|
Originally posted by: ybelov.yahoo.com
Walter Harley wrote:
> Equinox is an effort to provide a standalone OSGi implementation, in part by
> refactoring OSGi code that used to be in the Platform project into a
> separate project. In other words, Eclipse's OSGi implementation used to
> just be mixed in with the rest of Platform; Equinox separates it into its
> own project, for clarity and for the benefit of users who need just an OSGi
> implementation without the rest of Platform.
> As a result, many classes that used to be in org.eclipse.core.* plug-ins
> were moved to org.eclipse.equinox.* plug-ins. But the classes themselves
> are API so the package names can't easily be changed, and in fact those
> classes are re-exported from the old plug-ins via entries in the old plug-in
> manifests. For instance, org.eclipse.core.runtime imports
> org.eclipse.equinox.common and re-exports its contents.
> You can learn more by following the "Equinox" link from
> http://www.eclipse.org/eclipse/.
Thanks for the comprehensive explanation. Refactoring public API in a
modular open-source environment is a nightmare, it seems.
|
|
|
|
Powered by
FUDForum. Page generated in 0.10316 seconds
] 
Search
Help
Register
Login
Home
