You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Tong Fin (JIRA)" <ui...@incubator.apache.org> on 2008/03/27 17:43:24 UTC
[jira] Commented: (UIMA-939) PEAR packaging eclipse plugin not
visible after installation
[ https://issues.apache.org/jira/browse/UIMA-939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12582727#action_12582727 ]
Tong Fin commented on UIMA-939:
-------------------------------
Since you are using Eclipse 3.3.2, please try the following to see what is wrong:
- Open Window->Show View->Other...-> PDE->Plug-in Dependencies
- In Plug-in Dependencies view, click on "Show State Status" icon at top-right. You will see a long list of plug-ins.
- Find "o.a.uima.pear" PEAR plugin and try to see if there is any "red dot" which means that there is some errors.
- If PEAR plugin has a red dot, expand the node to see the reason of the error.
- Tong
> PEAR packaging eclipse plugin not visible after installation
> ------------------------------------------------------------
>
> Key: UIMA-939
> URL: https://issues.apache.org/jira/browse/UIMA-939
> Project: UIMA
> Issue Type: Bug
> Components: Eclipse plugins
> Environment: Linux only
> Eclipse 3.3.2
> Reporter: Michael Baessler
> Fix For: 2.2.2
>
>
> After installing the plugin, it is not available. The log file does not contain any entries.
> The error occurs only on Linux in eclipse 3.3.2. When using eclipse 3.2.2 all works fine
> Is there anything I can check to see what's wrong?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Commented: (UIMA-939) PEAR packaging eclipse plugin not
visible after installation
Posted by Marshall Schor <ms...@schor.com>.
Marshall Schor wrote:
> Michael Baessler wrote:
>> Tong Fin (JIRA) wrote:
>>
>>> [
>>> https://issues.apache.org/jira/browse/UIMA-939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12582727#action_12582727
>>> ]
>>> Tong Fin commented on UIMA-939:
>>> -------------------------------
>>>
>>> Since you are using Eclipse 3.3.2, please try the following to see
>>> what is wrong:
>>> - Open Window->Show View->Other...-> PDE->Plug-in Dependencies
>>> - In Plug-in Dependencies view, click on "Show State Status" icon
>>> at top-right. You will see a long list of plug-ins.
>>> - Find "o.a.uima.pear" PEAR plugin and try to see if there is any
>>> "red dot" which means that there is some errors.
>>> - If PEAR plugin has a red dot, expand the node to see the reason
>>> of the error.
>>>
>>> - Tong
>>>
>>>
>>>> PEAR packaging eclipse plugin not visible after installation
>>>> ------------------------------------------------------------
>>>>
>>>> Key: UIMA-939
>>>> URL: https://issues.apache.org/jira/browse/UIMA-939
>>>> Project: UIMA
>>>> Issue Type: Bug
>>>> Components: Eclipse plugins
>>>> Environment: Linux only Eclipse 3.3.2
>>>> Reporter: Michael Baessler
>>>> Fix For: 2.2.2
>>>>
>>>>
>>>> After installing the plugin, it is not available. The log file does
>>>> not contain any entries.
>>>> The error occurs only on Linux in eclipse 3.3.2. When using eclipse
>>>> 3.2.2 all works fine
>>>> Is there anything I can check to see what's wrong?
>>>>
>> After fixing some EMF dependencies after updates the plugin dependencies
>> look good. But when trying to call generatePearPackage I got the
>> following NoClassDefFoundError:
>>
>> java.lang.NoClassDefFoundError:
>> org/eclipse/ui/model/WorkbenchContentProvider
>>
> This may be a "Wiring" issue. I will look to see if the package
> "org.eclipse.ui.model" is available from more than one "bundle" in
> Eclipse 3.3.2. If so, then I will put in a simple change to specify
> the right bundle it should come from (the right one being the one
> which has the class WorkbenchContentProvider).
It looks like in Eclipse 3.3.2 (and maybe others), the package
"org.eclipse.ui.model" is available from bundle org.eclipse.ui.ide and
org.eclipse.ui.workbench. The WorkbenchContentProvider has to come from
org.eclipse.ui.ide.
Rather than pick these off one by one :-) I found a table in the Eclipse
"Help" by searching with the key words:
map split packages
This table lists all the split packages. For these cases, if there is
an import for this, the best fix I think is to add a Require-Bundle for
*all* the bundles that export this package. This will cover the case
where the CDE or other plugin might be actually using classes from more
than one of the bundles where this package is split.
(Previously, we were fixing these by wiring the need for a package to
just one of the bundles). The OSGi spec says this is permitted:
A given package may be available from more than one of the required bundles.
Such packages are named split packages because they derive their contents
from different bundles. If these different bundles provide the same
classes unpredictable shadowing of classes can arise, see Issues With
Requiring
Bundles on page 66. However, split packages without shadowing are
explicitly permitted.
Even better yet, reading the "Notes" to the table in this "Help" entry,
it is possible (in some cases) to specify a particular bundle which
will, in turn, import and then re-export the packages.
There are 4 packages in org.eclipse.jface.* that are "split" between
bundles org.eclipse.jface.text and org.eclipse.text. For these, we'll
require both bundles.
This is one package, org.eclipse.ui.texteditor that is split between
org.eclipse.ui.editors and org.eclipse.ui.workbench.texteditor. For
this, we'll require both bundles.
There are 5 packages in org.eclipse.ui.* that are split between
org.eclipse.ui.ide and org.eclipse.ui.workbench. The Notes say not to
require org.eclipse.ui.workbench, but instead just export org.eclipse.ui
(which imports and reexports org.eclipse.ui.workbench packages).
I'll make these changes for the plugins that currently import packages
that are split.
-Marshall
Re: [jira] Commented: (UIMA-939) PEAR packaging eclipse plugin not
visible after installation
Posted by Marshall Schor <ms...@schor.com>.
Michael Baessler wrote:
> Tong Fin (JIRA) wrote:
>
>> [ https://issues.apache.org/jira/browse/UIMA-939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12582727#action_12582727 ]
>>
>> Tong Fin commented on UIMA-939:
>> -------------------------------
>>
>> Since you are using Eclipse 3.3.2, please try the following to see what is wrong:
>> - Open Window->Show View->Other...-> PDE->Plug-in Dependencies
>> - In Plug-in Dependencies view, click on "Show State Status" icon at top-right. You will see a long list of plug-ins.
>> - Find "o.a.uima.pear" PEAR plugin and try to see if there is any "red dot" which means that there is some errors.
>> - If PEAR plugin has a red dot, expand the node to see the reason of the error.
>>
>> - Tong
>>
>>
>>> PEAR packaging eclipse plugin not visible after installation
>>> ------------------------------------------------------------
>>>
>>> Key: UIMA-939
>>> URL: https://issues.apache.org/jira/browse/UIMA-939
>>> Project: UIMA
>>> Issue Type: Bug
>>> Components: Eclipse plugins
>>> Environment: Linux only
>>> Eclipse 3.3.2
>>> Reporter: Michael Baessler
>>> Fix For: 2.2.2
>>>
>>>
>>> After installing the plugin, it is not available. The log file does not contain any entries.
>>> The error occurs only on Linux in eclipse 3.3.2. When using eclipse 3.2.2 all works fine
>>> Is there anything I can check to see what's wrong?
>>>
> After fixing some EMF dependencies after updates the plugin dependencies
> look good. But when trying to call generatePearPackage I got the
> following NoClassDefFoundError:
>
> java.lang.NoClassDefFoundError:
> org/eclipse/ui/model/WorkbenchContentProvider
>
This may be a "Wiring" issue. I will look to see if the package
"org.eclipse.ui.model" is available from more than one "bundle" in
Eclipse 3.3.2. If so, then I will put in a simple change to specify the
right bundle it should come from (the right one being the one which has
the class WorkbenchContentProvider).
-Marshall
Re: [jira] Commented: (UIMA-939) PEAR packaging eclipse plugin not
visible after installation
Posted by Michael Baessler <mb...@michael-baessler.de>.
Tong Fin (JIRA) wrote:
> [ https://issues.apache.org/jira/browse/UIMA-939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12582727#action_12582727 ]
>
> Tong Fin commented on UIMA-939:
> -------------------------------
>
> Since you are using Eclipse 3.3.2, please try the following to see what is wrong:
> - Open Window->Show View->Other...-> PDE->Plug-in Dependencies
> - In Plug-in Dependencies view, click on "Show State Status" icon at top-right. You will see a long list of plug-ins.
> - Find "o.a.uima.pear" PEAR plugin and try to see if there is any "red dot" which means that there is some errors.
> - If PEAR plugin has a red dot, expand the node to see the reason of the error.
>
> - Tong
>
>> PEAR packaging eclipse plugin not visible after installation
>> ------------------------------------------------------------
>>
>> Key: UIMA-939
>> URL: https://issues.apache.org/jira/browse/UIMA-939
>> Project: UIMA
>> Issue Type: Bug
>> Components: Eclipse plugins
>> Environment: Linux only
>> Eclipse 3.3.2
>> Reporter: Michael Baessler
>> Fix For: 2.2.2
>>
>>
>> After installing the plugin, it is not available. The log file does not contain any entries.
>> The error occurs only on Linux in eclipse 3.3.2. When using eclipse 3.2.2 all works fine
>> Is there anything I can check to see what's wrong?
>
After fixing some EMF dependencies after updates the plugin dependencies
look good. But when trying to call generatePearPackage I got the
following NoClassDefFoundError:
java.lang.NoClassDefFoundError:
org/eclipse/ui/model/WorkbenchContentProvider
at
org.apache.uima.pear.generate.PearFileResourceExportPage.createTreeViewer(PearFileResourceExportPage.java:368)
at
org.apache.uima.pear.generate.PearFileResourceExportPage.createSourceControl(PearFileResourceExportPage.java:274)
at
org.apache.uima.pear.generate.PearFileResourceExportPage.createControl(PearFileResourceExportPage.java:235)
at
org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:170)
at
org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:669)
at
org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:543)
at org.eclipse.jface.window.Window.create(Window.java:426)
at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1083)
at org.eclipse.jface.window.Window.open(Window.java:785)
at
org.apache.uima.pear.actions.GeneratePearFileAction.run(GeneratePearFileAction.java:89)
at
org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:256)
at
org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:546)
at
org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:490)
at
org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:402)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1101)
at
org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3319)
at
org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2971)
at
org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219)
at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466)
at
org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289)
at
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461)
at
org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at
org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106)
at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:169)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:508)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:447)
at org.eclipse.equinox.launcher.Main.run(Main.java:1173)
at org.eclipse.equinox.launcher.Main.main(Main.java:1148)
I hope that these are also some setup issues :-)
-- Michael