eclipse-sig January 2016

eclipse-sig@lists.fedoraproject.org

2 participants
79 discussions

Broken dependencies: eclipse-jbosstools
by Fedora Koji Build System 15 Jan '16

15 Jan '16

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.

1 0

[Bug 1298400] New: jetty-9.3.7.RC1 is available
by Red Hat Bugzilla 14 Jan '16

14 Jan '16

https://bugzilla.redhat.com/show_bug.cgi?id=1298400 Bug ID: 1298400 Summary: jetty-9.3.7.RC1 is available Product: Fedora Version: rawhide Component: jetty Keywords: FutureFeature, Triaged Assignee: mizdebsk(a)redhat.com Reporter: upstream-release-monitoring(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: eclipse-sig(a)lists.fedoraproject.org, java-sig-commits(a)lists.fedoraproject.org, krzysztof.daniel(a)gmail.com, mizdebsk(a)redhat.com, msimacek(a)redhat.com, msrb(a)redhat.com Latest upstream release: 9.3.7.RC1 Current version/release in rawhide: 9.3.7-0.1.RC0.fc24 URL: http://repo2.maven.org/maven2/org/eclipse/jetty/jetty-project/ 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. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=CEXmfrEVVX&a=cc_unsubscribe

1 4

Broken dependencies: eclipse-jbosstools
by Fedora Koji Build System 14 Jan '16

14 Jan '16

1 0

Broken dependencies: eclipse-jbosstools
by Fedora Koji Build System 13 Jan '16

13 Jan '16

1 0

Broken dependencies: eclipse-jbosstools
by Fedora Koji Build System 12 Jan '16

12 Jan '16

1 0

[Bug 1296699] New: Eclipse 4.5 unbearably slow under GTK3
by Red Hat Bugzilla 11 Jan '16

11 Jan '16

https://bugzilla.redhat.com/show_bug.cgi?id=1296699 Bug ID: 1296699 Summary: Eclipse 4.5 unbearably slow under GTK3 Product: Fedora Version: 23 Component: eclipse Assignee: akurtako(a)redhat.com Reporter: awood(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, rgrunber(a)redhat.com Created attachment 1112624 --> https://bugzilla.redhat.com/attachment.cgi?id=1112624&action=edit Thread dump of Eclipse while attempting to run debugger. Description of problem: Eclipse 4.5 (Mars) runs unbearably slowly under GTK3. The problem manifests most significantly for me in the debugger, although I do notice it to some extant when importing projects. Version-Release number of selected component (if applicable): % rpm -q eclipse-platform gtk3 eclipse-platform-4.5.1-6.fc23.x86_64 gtk3-3.18.6-1.fc23.x86_64 How reproducible: Unsure. It seems to be working fine on a laptop I have, but on my desktop, performance is consistently poor. Steps to Reproduce: 1. Install eclipse-platform and eclipse-jdt 2. Import a project, create a breakpoint on a class, and then run something that would hit that breakpoint. E.g. a unit test. Actual results: The debugger never even connects to the JVM or if it does, it's so sluggish as to be unusable. Expected results: Working debugger. Additional info: If I use the same workspace, same ~/.eclipse, and just run `eclipse eclipse --launcher.GTK_version 2` everything works and is quite fast. I've taken a thread dump (attached) and when using the VisualVM profiler, I see that 33% of the time is spent in org.eclipse.swt.internal.gtk.OS._gdk_window_get_origin[native] with an additional 28% in org.eclipse.swt.internal.gtk.OS._gdk_cairo_region_create_from_surface[native] Please let me know any additional information you might need and I will be happy to provide it. -- 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=7cYwPvKK5s&a=cc_unsubscribe

1 4

[Bug 1296869] New: Completions unreadable (white on white) for variable completions after method completed
by Red Hat Bugzilla 11 Jan '16

11 Jan '16

https://bugzilla.redhat.com/show_bug.cgi?id=1296869 Bug ID: 1296869 Summary: Completions unreadable (white on white) for variable completions after method completed Product: Fedora Version: 23 Component: eclipse Assignee: akurtako(a)redhat.com Reporter: sgehwolf(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, rgrunber(a)redhat.com Created attachment 1112830 --> https://bugzilla.redhat.com/attachment.cgi?id=1112830&action=edit screenshot for issue with unreadable possibilities for method params. Description of problem: I'm seeing a strange issue which shows up once I use code completions for a method and then see the possibilities for variables the method takes which are in current scope. The possibilities listed are unreadable since they are white on white background. Version-Release number of selected component (if applicable): eclipse-platform-4.5.1-6.fc23.x86_64 How reproducible: 100% Steps to Reproduce: 1. Create a string variable in some method in Eclipse JDT 2. Be sure to have some int variables in scope suitable for substring params 3. Hit <variable-name> + "." for the string variable. This should show auto-completion with all suitable methods on a string. 4. Select method "substring(int beginIndex, int endIndex)". 5. The input focus should move to the first param in method substring (beginIndex) and some possibilities should show up. At this point you should have it reproduced. Actual results: One only sees some red-icons with the variable names being white on white background. Thus, variables are unreadable. See attached screenshot. Expected results: Variable names readable, for example black on white background. -- 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=uOKSVJ5vru&a=cc_unsubscribe

1 5

Broken dependencies: eclipse-jbosstools
by Fedora Koji Build System 11 Jan '16

11 Jan '16

1 0

Broken dependencies: eclipse-jbosstools
by Fedora Koji Build System 10 Jan '16

10 Jan '16

1 0

Broken dependencies: eclipse-jbosstools
by Fedora Koji Build System 09 Jan '16

09 Jan '16

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

eclipse-sig January 2016