Home » Eclipse Projects » Eclipse Platform » Tracking plugin loading errors?
| Tracking plugin loading errors? [message #490830] |
Sun, 11 October 2009 12:58  |
Eclipse User |
|
|
|
I saw a long thread on "ignored plugins" earlier, but I am seeing a somewhat
different problem. I have set of plugins I am developing. The are not
installed (yet). In an older sandbox (i.e. Workspace), the plugin in
question loads when I launch the run-time workbench and everything is fine.
In the new sandbox, Eclipse ignores the plugin. In both cases, all looks
identical. This is on my Mac. On windows, everything works fine - both old
and new sandboxes (i.e. Workspaces). To me, this all suggests environment
(JVM, etc.) which is where I am looking. I have tried various options, such
as -clean. No soap.
But my question is, is there anyway to tell Eclipse to log the info as it
loads plugins? I am assuming it iterates through all the plugins, reading
the plugin.xml and Manifests and something is wrong. But there is no error
message, no log, nothing. Is there any way to force it to log this info?
Is there any efficient way to tackle this other than tedious inspection and
diffs?
TIA, Ric
|
|
| |
| Re: Tracking plugin loading errors? [message #490936 is a reply to message #490830] |
Mon, 12 October 2009 08:47  |
| Eclipse User |
|
|
|
Ric Wright wrote:
> I saw a long thread on "ignored plugins" earlier, but I am seeing a somewhat
> different problem. I have set of plugins I am developing. The are not
> installed (yet). In an older sandbox (i.e. Workspace), the plugin in
> question loads when I launch the run-time workbench and everything is fine.
> In the new sandbox, Eclipse ignores the plugin. In both cases, all looks
> identical. This is on my Mac. On windows, everything works fine - both old
> and new sandboxes (i.e. Workspaces). To me, this all suggests environment
> (JVM, etc.) which is where I am looking. I have tried various options, such
> as -clean. No soap.
>
Try -debug
Dani
> But my question is, is there anyway to tell Eclipse to log the info as it
> loads plugins? I am assuming it iterates through all the plugins, reading
> the plugin.xml and Manifests and something is wrong. But there is no error
> message, no log, nothing. Is there any way to force it to log this info?
> Is there any efficient way to tackle this other than tedious inspection and
> diffs?
>
> TIA, Ric
>
>
|
|
|
| Re: Tracking plugin loading errors? [message #491007 is a reply to message #490936] |
Mon, 12 October 2009 14:32 |
| Eclipse User |
|
|
|
Thanks guys. I tried both Michaels and Daniel's suggestions. I have made
some progress. Looks like some sort of JVM mismatch. Or at least, that's
what is seems since consoleLog claims all the unloaded plugins are
"unresolved". But that might be a red herring. Still digging.
Ric
On 10/12/09 5:47 AM, in article hav8g7$tc8$2@build.eclipse.org, "Daniel
Megert" <daniel_megert@ch.ibm.com> wrote:
> Ric Wright wrote:
>> I saw a long thread on "ignored plugins" earlier, but I am seeing a somewhat
>> different problem. I have set of plugins I am developing. The are not
>> installed (yet). In an older sandbox (i.e. Workspace), the plugin in
>> question loads when I launch the run-time workbench and everything is fine.
>> In the new sandbox, Eclipse ignores the plugin. In both cases, all looks
>> identical. This is on my Mac. On windows, everything works fine - both old
>> and new sandboxes (i.e. Workspaces). To me, this all suggests environment
>> (JVM, etc.) which is where I am looking. I have tried various options, such
>> as -clean. No soap.
>>
> Try -debug
>
> Dani
>> But my question is, is there anyway to tell Eclipse to log the info as it
>> loads plugins? I am assuming it iterates through all the plugins, reading
>> the plugin.xml and Manifests and something is wrong. But there is no error
>> message, no log, nothing. Is there any way to force it to log this info?
>> Is there any efficient way to tackle this other than tedious inspection and
>> diffs?
>>
>> TIA, Ric
>>
>>
|
|
|
| Re: Tracking plugin loading errors? [message #491008 is a reply to message #491007] |
Mon, 12 October 2009 14:47 |
| Eclipse User |
|
|
|
Well, made some progress and one of the plugins got resolved, so the
simplest plugin now works. But others still claim they are not "resolved".
One odd bit of info is that in the manifest of all the plugins - even the
ones that work - the Bundle-RequiredExecutionEnvironment: has a warning. It
is set to Bundle-RequiredExecutionEnvironment: J2SE-1.5. This is the
default on the Mac. The details for the warning say " The JRE container on
the classpath is not a perfect match to the 'J2SE-1.5' execution
environment". But if I go to the Library tab in the Build path dialog,
select the JRE, then the edit button, I get a dialog that lists Execution
Environments.If I select the "Environments..." Button, then choose J2SE1.5,
it gives me a list of options. One of them is the default JVM for the Mac,
which is listed as "a perfect match". But selecting that doesn't clear the
warning.
I suspect this area has something to do with the plugins that aren't working
"not being resolved", but am kind of stumped at this point. Still digging.
BTW, the plugin that works has this same warning, which suggests this too is
red herring...
Thanks, Ric
On 10/12/09 11:32 AM, in article C6F8C43F.3C066%riwright@adobe.com, "Ric
Wright" <riwright@adobe.com> wrote:
> Thanks guys. I tried both Michaels and Daniel's suggestions. I have made
> some progress. Looks like some sort of JVM mismatch. Or at least, that's
> what is seems since consoleLog claims all the unloaded plugins are
> "unresolved". But that might be a red herring. Still digging.
>
> Ric
>
>
> On 10/12/09 5:47 AM, in article hav8g7$tc8$2@build.eclipse.org, "Daniel
> Megert" <daniel_megert@ch.ibm.com> wrote:
>
>> Ric Wright wrote:
>>> I saw a long thread on "ignored plugins" earlier, but I am seeing a somewhat
>>> different problem. I have set of plugins I am developing. The are not
>>> installed (yet). In an older sandbox (i.e. Workspace), the plugin in
>>> question loads when I launch the run-time workbench and everything is fine.
>>> In the new sandbox, Eclipse ignores the plugin. In both cases, all looks
>>> identical. This is on my Mac. On windows, everything works fine - both old
>>> and new sandboxes (i.e. Workspaces). To me, this all suggests environment
>>> (JVM, etc.) which is where I am looking. I have tried various options, such
>>> as -clean. No soap.
>>>
>> Try -debug
>>
>> Dani
>>> But my question is, is there anyway to tell Eclipse to log the info as it
>>> loads plugins? I am assuming it iterates through all the plugins, reading
>>> the plugin.xml and Manifests and something is wrong. But there is no error
>>> message, no log, nothing. Is there any way to force it to log this info?
>>> Is there any efficient way to tackle this other than tedious inspection and
>>> diffs?
>>>
>>> TIA, Ric
>>>
>>>
>
|
|
|
| Re: Tracking plugin loading errors? [message #491069 is a reply to message #491007] |
Tue, 13 October 2009 02:41 |
| Eclipse User |
|
|
|
Ric Wright wrote:
> Thanks guys. I tried both Michaels and Daniel's suggestions. I have made
> some progress. Looks like some sort of JVM mismatch. Or at least, that's
> what is seems since consoleLog claims all the unloaded plugins are
> "unresolved". But that might be a red herring. Still digging.
>
Can you attach the console output here? And also check the .log file.
Dani
> Ric
>
>
> On 10/12/09 5:47 AM, in article hav8g7$tc8$2@build.eclipse.org, "Daniel
> Megert" <daniel_megert@ch.ibm.com> wrote:
>
>
>> Ric Wright wrote:
>>
>>> I saw a long thread on "ignored plugins" earlier, but I am seeing a somewhat
>>> different problem. I have set of plugins I am developing. The are not
>>> installed (yet). In an older sandbox (i.e. Workspace), the plugin in
>>> question loads when I launch the run-time workbench and everything is fine.
>>> In the new sandbox, Eclipse ignores the plugin. In both cases, all looks
>>> identical. This is on my Mac. On windows, everything works fine - both old
>>> and new sandboxes (i.e. Workspaces). To me, this all suggests environment
>>> (JVM, etc.) which is where I am looking. I have tried various options, such
>>> as -clean. No soap.
>>>
>>>
>> Try -debug
>>
>> Dani
>>
>>> But my question is, is there anyway to tell Eclipse to log the info as it
>>> loads plugins? I am assuming it iterates through all the plugins, reading
>>> the plugin.xml and Manifests and something is wrong. But there is no error
>>> message, no log, nothing. Is there any way to force it to log this info?
>>> Is there any efficient way to tackle this other than tedious inspection and
>>> diffs?
>>>
>>> TIA, Ric
>>>
>>>
>>>
>
>
|
|
|
| Re: Tracking plugin loading errors? [message #491176 is a reply to message #491069] |
Tue, 13 October 2009 10:35 |
| Eclipse User |
|
|
|
OK, I seem to have finally resolved this. There were two errors. One was a
misconfiguration of the manifest in my JOGL plugin (which IS installed in
the eclipse/plugin folder - there was no Bundle-NativeCode: declaration. I
believe that had no relation to this problem but was causing a real runtime
error with OpenGL).
But the cause of the problems in general was the mismatch between what
Eclipse saw as the required execution environment and what the manifest was
declaring. The default for Mac (in Leopard, 10.5) is JVM 1.5.0 (as noted
below). This has to be declared (apparently) in the Manifest.mf as
J2SE-1.5. In a couple of cases, the Manifest.mf still declared J2SE-1.6
_DESPITE_ the fact that I had edited the build properties library tab to
select the default JVM. So I guess that tab doesn't set the Manifest.mf
line? What does? The interrelationships between the build.properties,
Manifest.mf, and plugin.xml and the PDE panels seems a little byzantine at
times. It's a bit tricky I know as I have been building a PDE-style
multipage editor which has an underlying XML file and keeping it all in
synch is tricky. But perhaps I misunderstand how it is supposed to work.
Thanks for the various suggestions.
Ric
On 10/12/09 11:41 PM, in article hb17f0$6h3$1@build.eclipse.org, "Daniel
Megert" <daniel_megert@ch.ibm.com> wrote:
> Ric Wright wrote:
>> Thanks guys. I tried both Michaels and Daniel's suggestions. I have made
>> some progress. Looks like some sort of JVM mismatch. Or at least, that's
>> what is seems since consoleLog claims all the unloaded plugins are
>> "unresolved". But that might be a red herring. Still digging.
>>
> Can you attach the console output here? And also check the .log file.
>
> Dani
>> Ric
>>
>>
>> On 10/12/09 5:47 AM, in article hav8g7$tc8$2@build.eclipse.org, "Daniel
>> Megert" <daniel_megert@ch.ibm.com> wrote:
>>
>>
>>> Ric Wright wrote:
>>>
>>>> I saw a long thread on "ignored plugins" earlier, but I am seeing a
>>>> somewhat
>>>> different problem. I have set of plugins I am developing. The are not
>>>> installed (yet). In an older sandbox (i.e. Workspace), the plugin in
>>>> question loads when I launch the run-time workbench and everything is fine.
>>>> In the new sandbox, Eclipse ignores the plugin. In both cases, all looks
>>>> identical. This is on my Mac. On windows, everything works fine - both
>>>> old
>>>> and new sandboxes (i.e. Workspaces). To me, this all suggests environment
>>>> (JVM, etc.) which is where I am looking. I have tried various options,
>>>> such
>>>> as -clean. No soap.
>>>>
>>>>
>>> Try -debug
>>>
>>> Dani
>>>
>>>> But my question is, is there anyway to tell Eclipse to log the info as it
>>>> loads plugins? I am assuming it iterates through all the plugins, reading
>>>> the plugin.xml and Manifests and something is wrong. But there is no error
>>>> message, no log, nothing. Is there any way to force it to log this info?
>>>> Is there any efficient way to tackle this other than tedious inspection and
>>>> diffs?
>>>>
>>>> TIA, Ric
>>>>
>>>>
>>>>
>>
>>
|
|
|
Goto Forum:
Current Time: Tue Jul 22 19:38:40 EDT 2025
Powered by FUDForum. Page generated in 0.05621 seconds |
Home