[Bug 1286379] New: Issues with pydev editor and outline
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1286379
Bug ID: 1286379
Summary: Issues with pydev editor and outline
Product: Fedora
Version: 23
Component: eclipse-pydev
Assignee: akurtako(a)redhat.com
Reporter: rhbz(a)genodeftest.de
QA Contact: extras-qa(a)fedoraproject.org
CC: akurtako(a)redhat.com,
eclipse-sig(a)lists.fedoraproject.org,
jjohnstn(a)redhat.com, nathaniel(a)natemccallum.com
Description of problem:
The pydev eclipse plugin has many issues. This includes:
Outline does not link with editor after switching perspective:
Steps to reproduce:
1. open a python file in pydev perspective
2. check that outline and editor are linked and test. Should work fine
3. Switch to another perspective (e.g. Debug or C/C++)
4. test again. Now editor and outline are not linked any more.
Sometimes outline isn't even populated, although I cannot give exact steps to
reproduce.
Editor and Outline use different style than C/C++, Java, etc. Seems like pydev
is creating its own components (discouraged) instead of reusing existing ones.
Refactor is not sensitive to content and role in python files. It will always
try to search for all elements with same name in all files in current project.
Java and C/C++ editors are way better providing some semantic logic around
refactoring.
Version-Release number of selected component (if applicable):
eclipse-pydev-4.4.0-2.fc23.x86_64
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=SlX8wUwXYN&a=cc_unsubscribe
7 years, 11 months
[Bug 1202238] New: eclipse: Dropin cache not updated completely
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1202238
Bug ID: 1202238
Summary: eclipse: Dropin cache not updated completely
Product: Fedora
Version: rawhide
Component: eclipse
Assignee: rgrunber(a)redhat.com
Reporter: mizdebsk(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: akurtako(a)redhat.com, andjrobins(a)gmail.com,
eclipse-sig(a)lists.fedoraproject.org,
jerboaa(a)gmail.com, krzysztof.daniel(a)gmail.com,
mat.booth(a)redhat.com, msimacek(a)redhat.com,
rgrunber(a)redhat.com, swagiaal(a)redhat.com
Description of problem:
It looks like Eclipse Mars is caching dropins in ~/.eclipse and not refreshing
this cache entirely after dropin change (eg. package update).
Version-Release number of selected component (if applicable):
4.5.0-0.4.git201503030800
Steps to Reproduce:
1. rm -rf ~/.eclipse
2. install eclipse-m2e-core-1.6.0-0.1.fc23.noarch
3. run eclipse -data /tmp/new-workspace
4. close eclipse after it starts
5. update m2e to eclipse-m2e-core-1.6.0-0.2.fc23.noarch
6. re-run eclipse -data /tmp/new-workspace
Actual results:
There are a lot of exceptions printed on stdout, such as:
java.lang.RuntimeException: Unable to aquire PluginConverter service during
generation for:
/usr/share/eclipse/dropins/m2e-core/eclipse/plugins/org.eclipse.m2e.scm_1.6.0.20150312-2022.jar
These paths are refering to old m2e bundles from 1.6.0-0.1 which were removed
during eclipse-m2e-core package update.
Removing ~/.eclipse gets rid of these exceptions, so it looks like old paths
are cached there.
M2E works after update, so this is not critical. However accumulating warnings
like that clutters Eclipse stdout and makes noticing real problems more
difficult.
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=6eGilMjmu9&a=cc_unsubscribe
7 years, 11 months
[Bug 1210898] New: Eclipse tries to use non-existent Mozilla (xulrunner) browser
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1210898
Bug ID: 1210898
Summary: Eclipse tries to use non-existent Mozilla (xulrunner)
browser
Product: Fedora
Version: 21
Component: eclipse
Severity: high
Priority: high
Assignee: akurtako(a)redhat.com
Reporter: rgrunber(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: akurtako(a)redhat.com, andjrobins(a)gmail.com,
eclipse-sig(a)lists.fedoraproject.org,
jerboaa(a)gmail.com, krzysztof.daniel(a)gmail.com,
mat.booth(a)redhat.com, msimacek(a)redhat.com,
rgrunber(a)redhat.com, swagiaal(a)redhat.com
It looks like the user has some jboss-tools plugins installed that ultimately
try to bring up the browser. When it come sup, the user sees errors regarding
missing libswt-xulrunner. The call would seem to originate from
https://github.com/jbosstools/jbosstools-base/blob/master/runtime/plugins...
.
The other interesting part to note is that the BrowserFactory is returning the
Mozilla class, which could only happen if WebKit.IsInstalled () is false.
11:31 < k170> I keep getting an error in eclipse (luna), every time I try to
download and install a new server runtime.
11:33 < k170> The error states that it cannot find libswt-xulrunner-gtk.so
11:33 < k170> as well as libswt-xulrunner-gtk-4430.so
11:34 < k170> I'm running fedora 21 64bit and I have no idea how to install
those files
!ENTRY org.eclipse.ui 4 0 2015-04-09 21:52:39.606
!MESSAGE Unhandled event loop exception
!STACK 0
org.eclipse.swt.SWTError: No more handles (java.lang.UnsatisfiedLinkError:
Could not load SWT library. Reasons:
no swt-xulrunner-gtk-4430 in java.library.path
no swt-xulrunner-gtk in java.library.path
Can't load library:
/home/k170/.swt/lib/linux/x86_64/libswt-xulrunner-gtk-4430.so
Can't load library:
/home/k170/.swt/lib/linux/x86_64/libswt-xulrunner-gtk.so
)
at org.eclipse.swt.SWT.error(SWT.java:4467)
at org.eclipse.swt.SWT.error(SWT.java:4356)
at org.eclipse.swt.browser.Mozilla.initXULRunner(Mozilla.java:2745)
at org.eclipse.swt.browser.Mozilla.create(Mozilla.java:670)
at org.eclipse.swt.browser.Browser.<init>(Browser.java:99)
at
org.jboss.tools.runtime.ui.internal.wizard.DownloadRuntimeLicenseFragment.createComposite(DownloadRuntimeLicenseFragment.java:90)
at
org.jboss.tools.foundation.ui.xpl.taskwizard.TaskWizardPage.createControl(TaskWizardPage.java:44)
at
org.jboss.tools.foundation.ui.xpl.taskwizard.TaskWizard.createPageControls(TaskWizard.java:401)
at
org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:759)
at
org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:622)
at org.eclipse.jface.window.Window.create(Window.java:435)
at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1101)
at org.eclipse.jface.window.Window.open(Window.java:797)
at
org.jboss.tools.as.runtimes.integration.ui.composites.DownloadRuntimeHomeComposite$DownloadAndInstallListener.widgetSelected(DownloadRuntimeHomeComposite.java:75)
at
org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4454)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1412)
at org.eclipse.swt.widgets.Widget.sendSelectionEvent(Widget.java:1526)
at org.eclipse.swt.widgets.Link.gtk_button_release_event(Link.java:372)
at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:2078)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:5539)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:4668)
at org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(Native Method)
at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(OS.java:9106)
at org.eclipse.swt.widgets.Display.eventProc(Display.java:1253)
at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method)
at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:2477)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3407)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:832)
at org.eclipse.jface.window.Window.open(Window.java:808)
at
org.eclipse.wst.server.ui.internal.actions.LaunchWizardAction.run(LaunchWizardAction.java:57)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:519)
at
org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595)
at
org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511)
at
org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:420)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4454)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3799)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3409)
at
org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
at
org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at
org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
at
org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636)
at
org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at
org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135)
at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
Caused by: java.lang.UnsatisfiedLinkError: Could not load SWT library. Reasons:
no swt-xulrunner-gtk-4430 in java.library.path
no swt-xulrunner-gtk in java.library.path
Can't load library:
/home/k170/.swt/lib/linux/x86_64/libswt-xulrunner-gtk-4430.so
Can't load library:
/home/k170/.swt/lib/linux/x86_64/libswt-xulrunner-gtk.so
at org.eclipse.swt.internal.Library.loadLibrary(Library.java:321)
at org.eclipse.swt.internal.Library.loadLibrary(Library.java:242)
at org.eclipse.swt.browser.Mozilla.initXULRunner(Mozilla.java:2743)
... 61 more
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=Hc32FZ0PMz&a=cc_unsubscribe
7 years, 11 months
[Bug 1303912] New: drop dependency on WebKit 1 Gtk bindings
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1303912
Bug ID: 1303912
Summary: drop dependency on WebKit 1 Gtk bindings
Product: Fedora
Version: 23
Component: eclipse
Assignee: akurtako(a)redhat.com
Reporter: rhbz(a)genodeftest.de
QA Contact: extras-qa(a)fedoraproject.org
CC: akurtako(a)redhat.com, andjrobins(a)gmail.com,
eclipse-sig(a)lists.fedoraproject.org,
jerboaa(a)gmail.com, krzysztof.daniel(a)gmail.com,
mat.booth(a)redhat.com, rgrunber(a)redhat.com
Description of problem:
According to Michael Catanzaro, a developer of WebKitGtk, it is highly
discouraged to ever use WebKit 1 (webkitgtk package in Fedora) any more.
When running with Gtk2 backend, SWT is using this WebKit 1 Gtk binding.
Fedora's eclipse package should drop any webkitgtk dependency pretty soon. I
know that backwards compatibility is needed for some Eclipse plugins that
probably may require Gtk2 in-process with Eclipse/SWT. Is it possible to put
those outside the main eclipse-swt package? So "most" users won't see any
Webkit 1 Gtk bindings in Eclipse (and thus probably no Gtk2 version of
Eclipse). For those few who need that, they can install a separate (new)
package named e.g. eclipse-swt-gtk2.
Version-Release number of selected component (if applicable):
eclipse-swt-1:4.5.1-1.fc23
eclipse-swt-1:4.5.1-7.fc23
How reproducible:
always, see spec file
--
You are receiving this mail because:
You are on the CC list for the bug.
7 years, 11 months
[Bug 1310364] New: lucene-5.5.0 is available
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1310364
Bug ID: 1310364
Summary: lucene-5.5.0 is available
Product: Fedora
Version: rawhide
Component: lucene
Keywords: FutureFeature, Triaged
Assignee: akurtako(a)redhat.com
Reporter: upstream-release-monitoring(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: akurtako(a)redhat.com,
eclipse-sig(a)lists.fedoraproject.org,
hicham.haouari(a)gmail.com,
java-sig-commits(a)lists.fedoraproject.org,
jerboaa(a)gmail.com, krzysztof.daniel(a)gmail.com,
msimacek(a)redhat.com, puntogil(a)libero.it,
rgrunber(a)redhat.com
Latest upstream release: 5.5.0
Current version/release in rawhide: 5.4.1-3.fc24
URL: http://lucene.apache.org/
Please consult the package updates policy before you issue an update to a
stable branch: https://fedoraproject.org/wiki/Updates_Policy
More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring
Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.
--
You are receiving this mail because:
You are on the CC list for the bug.
8 years
[Bug 1226615] New: Quick Outline (Ctrl+O) doesn't work (Outline is closed immediately)
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1226615
Bug ID: 1226615
Summary: Quick Outline (Ctrl+O) doesn't work (Outline is closed
immediately)
Product: Fedora
Version: 22
Component: eclipse-cdt
Assignee: jjohnstn(a)redhat.com
Reporter: hedayatv(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: akurtako(a)redhat.com,
eclipse-sig(a)lists.fedoraproject.org,
jjohnstn(a)redhat.com, krzysztof.daniel(a)gmail.com,
rgrunber(a)redhat.com
Description of problem:
Eclipse in Fedora 22 has many problems (actually, mostly about its color theme
which is unreadable/unnoticable in some places), but one of the most annoying
ones is that the Quick Outline view (Ctrl+O) doesn't work. It does open the
outline window, but it is closed immediately. Also, it has a black background
while it was yellow (IIRC) in F21; but this is not that important.
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=C5gKD2cpuS&a=cc_unsubscribe
8 years
[Bug 1269892] New: [eclipse] text and icons are partially rendered on top of a white background.
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1269892
Bug ID: 1269892
Summary: [eclipse] text and icons are partially rendered on top
of a white background.
Product: Fedora
Version: 23
Component: eclipse
Assignee: akurtako(a)redhat.com
Reporter: jfrieben(a)hotmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: akurtako(a)redhat.com, andjrobins(a)gmail.com,
eclipse-sig(a)lists.fedoraproject.org,
jerboaa(a)gmail.com, krzysztof.daniel(a)gmail.com,
mat.booth(a)redhat.com, rgrunber(a)redhat.com
Created attachment 1080987
--> https://bugzilla.redhat.com/attachment.cgi?id=1080987&action=edit
Screenshot of eclipse sample dialog window
Description of problem:
The graphical user interface exhibits white patches here and there when the
overall background colour is a light grey.
Version-Release number of selected component (if applicable):
eclipse-4.5.1-1.fc23
How reproducible:
Always.
Steps to Reproduce:
1. Launch eclipse.
2. Create new Java project.
Actual results:
Text and icons are partially rendered on top of a white background.
Expected results:
Text and icons are rendered on top of the default light grey background.
Additional info:
None.
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=hTr4LIuq0J&a=cc_unsubscribe
8 years, 1 month
[Bug 1196736] New: eclipse gui white-unreadable text - changing colors too
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1196736
Bug ID: 1196736
Summary: eclipse gui white-unreadable text - changing colors
too
Product: Fedora
Version: 22
Component: eclipse-pdt
Severity: high
Assignee: mat.booth(a)redhat.com
Reporter: peljasz(a)yahoo.co.uk
QA Contact: extras-qa(a)fedoraproject.org
CC: eclipse-sig(a)lists.fedoraproject.org,
mat.booth(a)redhat.com
Created attachment 995677
--> https://bugzilla.redhat.com/attachment.cgi?id=995677&action=edit
snapshot of white text
Description of problem:
please take a look a the attached snap, I'd happy it says more than if I tried
to explain.
Also, the yellow background of the second windows changes to black, is yellow
only the first time is invoked, every subsequent invocation is black.
The white text is most troublesome as you cannot see what is says, row that
gets focus changes to white text.
I thought it was configurable somewhere but failed to find settings if there
are any.
Version-Release number of selected component (if applicable):
eclipse-emf-runtime-2.10.1-3.fc22.noarch
eclipse-xsd-2.10.1-3.fc22.noarch
eclipse-pdt-3.3.1-5.fc22.noarch
eclipse-equinox-osgi-4.4.1-17.fc22.x86_64
eclipse-pde-4.4.1-17.fc22.x86_64
eclipse-gef-3.9.101-3.fc22.noarch
eclipse-subclipse-1.10.5-2.fc22.noarch
eclipse-jdt-4.4.1-17.fc22.x86_64
eclipse-webtools-common-core-3.6.2-1.fc22.noarch
eclipse-dltk-5.1.0-6.fc22.noarch
eclipse-webtools-sourceediting-3.6.2-1.fc22.noarch
eclipse-rse-3.6.0-4.fc22.noarch
eclipse-platform-4.4.1-17.fc22.x86_64
eclipse-webtools-servertools-core-3.6.2-1.fc22.noarch
eclipse-webtools-common-3.6.2-1.fc22.noarch
eclipse-filesystem-1.0-3.fc22.x86_64
eclipse-dltk-rse-5.1.0-6.fc22.noarch
eclipse-swt-4.4.1-17.fc22.x86_64
eclipse-subclipse-graph-1.10.5-2.fc22.noarch
eclipse-emf-core-2.10.1-3.fc22.x86_64
eclipse-mylyn-3.14.2-1.fc22.noarch
eclipse-webtools-servertools-3.6.2-1.fc22.noarch
eclipse-dltk-mylyn-5.1.0-6.fc22.noarch
eclipse-ecf-core-3.9.2-2.fc22.x86_64
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=JkxqBUsj6O&a=cc_unsubscribe
8 years, 1 month
[Bug 1302131] New: eclipse-cdt-arduino entirely non-functional
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1302131
Bug ID: 1302131
Summary: eclipse-cdt-arduino entirely non-functional
Product: Fedora
Version: 23
Component: eclipse-cdt
Severity: urgent
Assignee: jjohnstn(a)redhat.com
Reporter: dwt(a)poltec.com
QA Contact: extras-qa(a)fedoraproject.org
CC: akurtako(a)redhat.com,
eclipse-sig(a)lists.fedoraproject.org,
jjohnstn(a)redhat.com, krzysztof.daniel(a)gmail.com,
rgrunber(a)redhat.com
Description of problem:
After installing the eclipse-cdt-arduino rpm, there is supposed to
be a prefences menu for it under Window->preferences->C/C++. It
is not there.
The plugin also doesn't show up under Help->Installation Details.
Version-Release number of selected component (if applicable):
eclipse-cdt-arduino-8.8.0-3.fc23.x86_64
How reproducible:
Always.
Steps to Reproduce:
1. Install eclipse-cdt-arduino-8.8.0-3.fc23.x86_64. (and btw, on a clean
system this of course pulls in all the necesary support including
eclipse-cdt, but also an extra 120 Megs or so by way of eclipse-jdt
and eclipse-pde...seriously, WTF???? Does the use of plugins really
require the plugin development environment??)
2. Look under Window->preferences->C/C++, observer no "Arduino" entry
3.
Actual results:
Plugin is neither usable nor discoverable.
Expected results:
Expected plugin to become available and work.
Additional info:
Erasing the cdt-arduino rpm and installing the plugin from the
Eclipse Marketplace works as expected. But this is a single
user only installation and not system wide, so that's somewhat
unsatisfactory.
The rpm drops its files in /usr/lib64/eclipse/dropins. Permissions
look OK, matching other plugins which do work. Moving the files into
reasonable places from cdt-arduino to cdt doesn't help. Neither does
renaming cdt-arduino to simply arduino. Maybe there's a manifest
that needs updating and the post-install scripts are missing it?
Being just a user, I don't know enough about the plugin system to
take any more guesses.
--
You are receiving this mail because:
You are on the CC list for the bug.
8 years, 1 month
Broken dependencies: eclipse-jbosstools
by Fedora Koji Build System
eclipse-jbosstools has broken dependencies in the rawhide tree:
On x86_64:
eclipse-jbosstools-as-4.2.2-1.fc22.noarch requires osgi(org.eclipse.tm.terminal)
On i386:
eclipse-jbosstools-as-4.2.2-1.fc22.noarch requires osgi(org.eclipse.tm.terminal)
On armhfp:
eclipse-jbosstools-as-4.2.2-1.fc22.noarch requires osgi(org.eclipse.tm.terminal)
Please resolve this as soon as possible.
8 years, 1 month