[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Newsgroup Home]
|
[news.eclipse.platform] Re: Plugin is instantiated but bundle is null
|
- From: Remy Chi Jian Suen <remy.suen@xxxxxxxxx>
- Date: Wed, 21 Nov 2007 08:11:01 -0500
- Newsgroups: eclipse.platform
- Organization: EclipseCorner
- User-agent: Pan/0.14.2 (This is not a psychotic episode. It's a cleansing moment of clarity.)
On Tue, 20 Nov 2007 18:17:33 +0000, Miles Daffin wrote:
> This one is driving me quite coo-coo. We have a plugin that function fine
> in 3.2. A lot of our users have just moved up to 3.3 and keep running into
> this NPE during initialization of java tooling:
>
> java.lang.NullPointerException
> at org.eclipse.core.runtime.Plugin$1.run(Plugin.java:353)
> at org.eclipse.core.runtime.Plugin.getPluginPreferences(Plugin.java:356)
>
> It seems like, under certain circumstances, the Plugin has been
> instantiated but the start method has not been called, hence the plugin's
> Bundle (bundle) is null. The call to bundleCopy.getSymbolicName()
> (Plugin.java:353) therefore throws the NPE.
Does your plug-in call super.start(context) in its own
start(BundleContext) implementation?
Regards,
Rem