eclipse-sig June 2019

eclipse-sig@lists.fedoraproject.org

2 participants
19 discussions

[Bug 1719748] New: jetty-9.4.19.v20190610 is available
by bugzilla＠redhat.com 15 Sep '22

15 Sep '22

https://bugzilla.redhat.com/show_bug.cgi?id=1719748 Bug ID: 1719748 Summary: jetty-9.4.19.v20190610 is available Product: Fedora Version: rawhide Status: NEW Component: jetty Keywords: FutureFeature, Triaged Assignee: mat.booth(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, jjohnstn(a)redhat.com, krzysztof.daniel(a)gmail.com, mat.booth(a)redhat.com, mizdebsk(a)redhat.com, sochotni(a)redhat.com Target Milestone: --- Classification: Fedora Latest upstream release: 9.4.19.v20190610 Current version/release in rawhide: 9.4.18-2.v20190429.fc31 URL: http://www.eclipse.org/jetty 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. Based on the information from anitya: https://release-monitoring.org/project/1447/ -- You are receiving this mail because: You are on the CC list for the bug.

1 23

[Bug 1683547] New: lucene-7.7.1 is available
by bugzilla＠redhat.com 23 Apr '21

23 Apr '21

https://bugzilla.redhat.com/show_bug.cgi?id=1683547 Bug ID: 1683547 Summary: lucene-7.7.1 is available Product: Fedora Version: rawhide Status: NEW 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, dbhole(a)redhat.com, dingyichen(a)gmail.com, eclipse-sig(a)lists.fedoraproject.org, java-sig-commits(a)lists.fedoraproject.org, jerboaa(a)gmail.com, krzysztof.daniel(a)gmail.com, lef(a)fedoraproject.org, rgrunber(a)redhat.com Target Milestone: --- Classification: Fedora Latest upstream release: 7.7.1 Current version/release in rawhide: 7.7.0-1.fc30 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. Based on the information from anitya: https://release-monitoring.org/project/7178/ -- You are receiving this mail because: You are on the CC list for the bug.

1 42

[Bug 1670518] New: Cannot start eclipse-platform-4.10.0-2.fc30.x86_64
by bugzilla＠redhat.com 24 Nov '20

24 Nov '20

https://bugzilla.redhat.com/show_bug.cgi?id=1670518 Bug ID: 1670518 Summary: Cannot start eclipse-platform-4.10.0-2.fc30.x86_64 Product: Fedora Version: rawhide Status: NEW Component: eclipse Assignee: mat.booth(a)redhat.com Reporter: lslebodn(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: akurtako(a)redhat.com, andjrobins(a)gmail.com, dbhole(a)redhat.com, ebaron(a)fedoraproject.org, eclipse-sig(a)lists.fedoraproject.org, jerboaa(a)gmail.com, jjohnstn(a)redhat.com, lef(a)fedoraproject.org, mat.booth(a)redhat.com, rgrunber(a)redhat.com Target Milestone: --- Classification: Fedora Created attachment 1524767 --> https://bugzilla.redhat.com/attachment.cgi?id=1524767&action=edit .metadata/.log Description of problem: I tried to start eclipse with empty workspace and it failed Version-Release number of selected component (if applicable): sh$ rpm -qa eclipse\* | sort eclipse-cdt-9.6.0-4.fc30.x86_64 eclipse-cdt-native-9.6.0-4.fc30.x86_64 eclipse-ecf-core-3.14.4-1.fc30.noarch eclipse-egit-5.2.0-1.fc30.noarch eclipse-emf-core-2.16.0-1.fc30.noarch eclipse-equinox-osgi-4.10.0-2.fc30.x86_64 eclipse-jdt-4.10.0-2.fc30.noarch eclipse-jgit-5.2.0-2.fc30.noarch eclipse-launchbar-2.2.2-1.fc30.noarch eclipse-linuxtools-libhover-7.1.0-1.fc30.noarch eclipse-platform-4.10.0-2.fc30.x86_64 eclipse-remote-3.0.0-0.6.git14c6611.fc30.noarch eclipse-rse-3.7.100-1.fc30.noarch eclipse-swt-4.10.0-2.fc30.x86_64 eclipse-tm-terminal-4.4.0-4.fc30.noarch eclipse-tm-terminal-connectors-4.4.0-4.fc30.noarch How reproducible: Deterministic on my machine (did not try on another laptop) Steps to Reproduce: 1. create empty directory in homedir 2. /usr/bin/eclipse 3. choose directory created in the 1st step as workspace Actual results: failed to open IDE Expected results: IDE started without any problem Additional info: there are some exceptions in .metadata/.log -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1704981] New: Eclipse cannot import maven projects
by bugzilla＠redhat.com 25 Aug '20

25 Aug '20

https://bugzilla.redhat.com/show_bug.cgi?id=1704981 Bug ID: 1704981 Summary: Eclipse cannot import maven projects Product: Fedora Version: 30 Hardware: x86_64 OS: Linux Status: NEW Component: eclipse-m2e-core Severity: high Assignee: mat.booth(a)redhat.com Reporter: proski(a)gnu.org QA Contact: extras-qa(a)fedoraproject.org CC: eclipse-sig(a)lists.fedoraproject.org, gerard(a)ryan.lt, mat.booth(a)redhat.com, mizdebsk(a)redhat.com Target Milestone: --- Classification: Fedora Description of problem: After updating to Fedora 30, Eclipse fails to import maven based projects Version-Release number of selected component (if applicable): eclipse-jdt-4.11-4.fc30.noarch eclipse-m2e-core-1.11.0-1.fc30.noarch How reproducible: Always Steps to Reproduce: 1. Run Eclipse 2. File->Import->Maven->Checkout Maven Projects from SCM 3. Enter https://github.com/jenkinsci/stash-pullrequest-builder-plugin.git and click "Finish Actual results: A message appears: An internal error occurred during: "Importing Maven projects". org.apache.lucene.document.Field.<init>(Ljava/lang/String;Ljava/lang/String;Lorg/apache/lucene/index/IndexableFieldType;)V Expected results: The project is imported successfully Additional info: Also tested with https://github.com/jenkinsci/stashnotifier-plugin.git Message from ~/workspace/.metadata/.log: !ENTRY org.eclipse.core.jobs 4 2 2019-04-30 16:42:11.456 !MESSAGE An internal error occurred during: "Importing Maven projects". !STACK 0 java.lang.NoSuchMethodError: org.apache.lucene.document.Field.<init>(Ljava/lang/String;Ljava/lang/String;Lorg/apache/lucene/index/IndexableFieldType;)V at org.apache.maven.index.IndexerField.toField(IndexerField.java:96) at org.apache.maven.index.creator.MinimalArtifactInfoIndexCreator.updateDocument(MinimalArtifactInfoIndexCreator.java:267) at org.apache.maven.index.ArtifactContext.createDocument(ArtifactContext.java:195) at org.apache.maven.index.DefaultIndexerEngine.update(DefaultIndexerEngine.java:72) at org.apache.maven.index.DefaultIndexer.addArtifactsToIndex(DefaultIndexer.java:109) at org.apache.maven.index.DefaultNexusIndexer.addArtifactToIndex(DefaultNexusIndexer.java:337) at org.eclipse.m2e.core.internal.index.nexus.NexusIndexManager.addDocument(NexusIndexManager.java:588) at org.eclipse.m2e.core.internal.index.nexus.NexusIndexManager.mavenProjectChanged(NexusIndexManager.java:767) at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.notifyProjectChangeListeners(ProjectRegistryManager.java:777) at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.applyMutableProjectRegistry(ProjectRegistryManager.java:921) at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.refresh(ProjectRegistryManager.java:298) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.configureNewMavenProjects(ProjectConfigurationManager.java:259) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$1.call(ProjectConfigurationManager.java:175) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$1.call(ProjectConfigurationManager.java:1) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:177) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151) at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:99) at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1336) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.importProjects(ProjectConfigurationManager.java:143) at org.eclipse.m2e.core.ui.internal.wizards.ImportMavenProjectsJob$1.doCreateMavenProjects(ImportMavenProjectsJob.java:68) at org.eclipse.m2e.core.ui.internal.wizards.AbstractCreateMavenProjectsOperation.run(AbstractCreateMavenProjectsOperation.java:73) at org.eclipse.m2e.core.ui.internal.wizards.ImportMavenProjectsJob.runInWorkspace(ImportMavenProjectsJob.java:77) at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:42) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63) -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 1705924] New: CVE-2019-10241 jetty: using specially formatted URL against DefaultServlet or ResourceHandler leads to XSS conditions
by bugzilla＠redhat.com 14 Apr '20

14 Apr '20

https://bugzilla.redhat.com/show_bug.cgi?id=1705924 Bug ID: 1705924 Summary: CVE-2019-10241 jetty: using specially formatted URL against DefaultServlet or ResourceHandler leads to XSS conditions Product: Security Response Hardware: All OS: Linux Status: NEW Whiteboard: impact=moderate,public=20190422,reported=20190423,sour ce=cve,cvss3=4.7/CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:N/ I:L/A:N,cwe=CWE-79,fedora-all/jetty=affected,rhel-6/je tty-eclipse=new,rhel-7/jetty=new,fuse-6/jetty=new,fuse -7/jetty=new,rhn_satellite_5/jetty=new,rhscl-3/rh-java -common-jetty=new Component: vulnerability Keywords: Security Severity: medium Priority: medium Assignee: security-response-team(a)redhat.com Reporter: mrehak(a)redhat.com CC: aileenc(a)redhat.com, bkearney(a)redhat.com, chazlett(a)redhat.com, decathorpe(a)gmail.com, eclipse-sig(a)lists.fedoraproject.org, ggainey(a)redhat.com, hhorak(a)redhat.com, janstey(a)redhat.com, java-maint(a)redhat.com, java-sig-commits(a)lists.fedoraproject.org, jjohnstn(a)redhat.com, jochrist(a)redhat.com, jorton(a)redhat.com, krzysztof.daniel(a)gmail.com, mizdebsk(a)redhat.com, sochotni(a)redhat.com, stewardship-sig(a)lists.fedoraproject.org, tlestach(a)redhat.com Target Milestone: --- Classification: Other In Eclipse Jetty version 9.2.26 and older, 9.3.25 and older, and 9.4.15 and older, the server is vulnerable to XSS conditions if a remote client USES a specially formatted URL against the DefaultServlet or ResourceHandler that is configured for showing a Listing of directory contents. External References: https://bugs.eclipse.org/bugs/show_bug.cgi?id=546121 -- You are receiving this mail because: You are on the CC list for the bug.

1 16

[Bug 1705993] New: CVE-2019-10247 jetty: error path information disclosure
by bugzilla＠redhat.com 14 Apr '20

14 Apr '20

https://bugzilla.redhat.com/show_bug.cgi?id=1705993 Bug ID: 1705993 Summary: CVE-2019-10247 jetty: error path information disclosure Product: Security Response Hardware: All OS: Linux Status: NEW Whiteboard: impact=moderate,public=20190418,reported=20190423,sour ce=cve,cvss3=5.3/CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/ I:N/A:N,cwe=CWE-200,fedora-all/jetty=affected,fuse-6/j etty=new,fuse-7/jetty=new,rhn_satellite_5/jetty=new,rh scl-3/rh-java-common-jetty=new,rhel-6/jetty-eclipse=ne w,rhel-7/jetty=new Component: vulnerability Keywords: Security Severity: medium Priority: medium Assignee: security-response-team(a)redhat.com Reporter: darunesh(a)redhat.com CC: aileenc(a)redhat.com, bkearney(a)redhat.com, chazlett(a)redhat.com, decathorpe(a)gmail.com, eclipse-sig(a)lists.fedoraproject.org, ggainey(a)redhat.com, hhorak(a)redhat.com, janstey(a)redhat.com, java-maint(a)redhat.com, java-sig-commits(a)lists.fedoraproject.org, jjohnstn(a)redhat.com, jochrist(a)redhat.com, jorton(a)redhat.com, krzysztof.daniel(a)gmail.com, mizdebsk(a)redhat.com, sochotni(a)redhat.com, stewardship-sig(a)lists.fedoraproject.org, tlestach(a)redhat.com Target Milestone: --- Classification: Other In Eclipse Jetty version 7.x, 8.x, 9.2.27 and older, 9.3.26 and older, and 9.4.16 and older, the server running on any OS and Jetty version combination will reveal the configured fully qualified directory base resource location on the output of the 404 error for not finding a Context that matches the requested path. The default server behavior on jetty-distribution and jetty-home will include at the end of the Handler tree a DefaultHandler, which is responsible for reporting this 404 error, it presents the various configured contexts as HTML for users to click through to. This produced HTML includes output that contains the configured fully qualified directory base resource location for each context. Reference: https://bugs.eclipse.org/bugs/show_bug.cgi?id=546577 -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Bug 1696062] New: CVE-2018-12545 jetty: large settings frames causing denial of service
by bugzilla＠redhat.com 11 Dec '19

11 Dec '19

https://bugzilla.redhat.com/show_bug.cgi?id=1696062 Bug ID: 1696062 Summary: CVE-2018-12545 jetty: large settings frames causing denial of service Product: Security Response Hardware: All OS: Linux Status: NEW Whiteboard: impact=moderate,public=20190320,reported=20190328,sour ce=cve,cvss3=4.2/CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:N/ I:L/A:L,cwe=CWE-400,fedora-all/jetty=affected,rhel-6/j etty-eclipse=notaffected,rhel-7/jetty=new,fuse-6/jetty =affected,fuse-7/jetty=affected,rhn_satellite_5/jetty= affected,rhscl-3/rh-java-common-jetty=affected Component: vulnerability Keywords: Security Severity: medium Priority: medium Assignee: security-response-team(a)redhat.com Reporter: darunesh(a)redhat.com CC: bkearney(a)redhat.com, chazlett(a)redhat.com, decathorpe(a)gmail.com, eclipse-sig(a)lists.fedoraproject.org, ggainey(a)redhat.com, hhorak(a)redhat.com, java-maint(a)redhat.com, java-sig-commits(a)lists.fedoraproject.org, jjohnstn(a)redhat.com, jorton(a)redhat.com, krzysztof.daniel(a)gmail.com, mizdebsk(a)redhat.com, sochotni(a)redhat.com, stewardship-sig(a)lists.fedoraproject.org, tlestach(a)redhat.com Target Milestone: --- Classification: Other In Eclipse Jetty version 9.3.x and 9.4.x, the server is vulnerable to Denial of Service conditions if a remote client sends either large SETTINGs frames container containing many settings, or many small SETTINGs frames. The vulnerability is due to the additional CPU and memory allocations required to handle changed settings Reference: https://bugs.eclipse.org/bugs/show_bug.cgi?id=538096 -- You are receiving this mail because: You are on the CC list for the bug.

1 14

[Bug 1670838] New: Running the an Eclipse PDE example throws a null pointer exception.
by bugzilla＠redhat.com 27 Nov '19

27 Nov '19

https://bugzilla.redhat.com/show_bug.cgi?id=1670838 Bug ID: 1670838 Summary: Running the an Eclipse PDE example throws a null pointer exception. Product: Fedora Version: 29 Hardware: All OS: Linux Status: NEW Component: eclipse Severity: high Assignee: mat.booth(a)redhat.com Reporter: harry.terzian(a)imgtec.com QA Contact: extras-qa(a)fedoraproject.org CC: akurtako(a)redhat.com, andjrobins(a)gmail.com, dbhole(a)redhat.com, ebaron(a)fedoraproject.org, eclipse-sig(a)lists.fedoraproject.org, jerboaa(a)gmail.com, jjohnstn(a)redhat.com, lef(a)fedoraproject.org, mat.booth(a)redhat.com, rgrunber(a)redhat.com Target Milestone: --- Classification: Fedora Description of problem: Using the Eclipse through the dnf channel is not working as expected: I am attempting to build a simple hello world application by creating a new eclipse plugin project and selecting the template of "View contribution using 4.x API". Building and running that example as it is with no modification does not work as I am getting the following error message: !MESSAGE Possbible annotation mismatch: method "public void hello.parts.SampleView.createPartControl(org.eclipse.swt.widgets.Composite)" annotated with "javax.annotation-api:1.2.0:javax.annotation.PostConstruct" but was looking for "javax.annotation.PostConstruct [via bootstrap classloader]" Looking at the jar files within the eclipse /usr/lib/eclipse/plugins I noticed that there are jar files pointing to glassfish: /usr/lib/eclipse/plugins/javax.annotation-api_1.2.0.jar -> /usr/share/java/glassfish-annotation-api.jar /usr/lib/eclipse/plugins/javax.el-api_3.0.0.jar -> /usr/share/java/glassfish-el-api.jar /usr/lib/eclipse/plugins/javax.inject_1.0.0.v20091030.jar -> /usr/share/java/atinject.jar /usr/lib/eclipse/plugins/javax.servlet-api_3.1.0.jar -> /usr/share/java/glassfish-servlet-api.jar /usr/lib/eclipse/plugins/javax.servlet.jsp_2.3.2.b01.jar -> /usr/share/java/glassfish-jsp-api/javax.servlet.jsp-api.jar specifically the javax.annotation-api_1.2.0.jar is different from the other Eclipse downloaded from https://www.eclipse.org/downloads/packages It comes as javax.annotation_1.2.0.v201602091430.jar which is differen Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Open eclipse 2. Create a new eclipse plugin project using the template of View contribution using 4.x API". 3. Run the example Actual results: A view is created which throws a null pointer exception. Expected results: A view which displays some text. Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1670222] New: Eclipse help browser unusable due to hard-coded font size being unreadably small
by bugzilla＠redhat.com 27 Nov '19

27 Nov '19

https://bugzilla.redhat.com/show_bug.cgi?id=1670222 Bug ID: 1670222 Summary: Eclipse help browser unusable due to hard-coded font size being unreadably small Product: Fedora Version: 29 Hardware: x86_64 OS: Linux Status: NEW Component: eclipse Severity: high Assignee: mat.booth(a)redhat.com Reporter: dwt(a)poltec.com QA Contact: extras-qa(a)fedoraproject.org CC: akurtako(a)redhat.com, andjrobins(a)gmail.com, dbhole(a)redhat.com, ebaron(a)fedoraproject.org, eclipse-sig(a)lists.fedoraproject.org, jerboaa(a)gmail.com, jjohnstn(a)redhat.com, lef(a)fedoraproject.org, mat.booth(a)redhat.com, rgrunber(a)redhat.com Target Milestone: --- Classification: Fedora Description of problem: Eclipse help browser fonts are unreadably small Version-Release number of selected component (if applicable): eclipse-platform-4.10.0-2.fc29.x86_64 How reproducible: Always Steps to Reproduce: 1. Launch Eclipse 2. Help=>Help Contents 3. Help browser will open, note size of font in content pane Actual results: On a 1080p laptop screen the content font is < 1mm high Expected results: The help browser should be helpful and use a readably-sized font, and beyond that should be user configurable like pretty much everything else in eclipse Additional info: This has actually been true since at least fedora 23, though back then I didn't notice when using a lower resolution screen, and may not have had much occasion to open the help browser anyway. The help font resists being changed by any method; it's like it's hard-wired into the code. Nothing under windows=>preferences=>colors and fonts seems to have any effect. There are some promising-looking css files under ~/.eclipse, but changing all the font sizes to something huge does nothing. The only thing which touches this problem is to set the desktop (Mate) font rendering dpi to something ridiculously high, like 200 or 300, but then everything else is scaled up absurdly. -- You are receiving this mail because: You are on the CC list for the bug.

1 14

[Bug 1667654] New: Eclipse Update failed
by bugzilla＠redhat.com 27 Nov '19

27 Nov '19

https://bugzilla.redhat.com/show_bug.cgi?id=1667654 Bug ID: 1667654 Summary: Eclipse Update failed Product: Fedora Version: 29 Hardware: x86_64 OS: Linux Status: NEW Component: eclipse Severity: high Assignee: mat.booth(a)redhat.com Reporter: abhijit4daksh(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: akurtako(a)redhat.com, andjrobins(a)gmail.com, dbhole(a)redhat.com, ebaron(a)fedoraproject.org, eclipse-sig(a)lists.fedoraproject.org, jerboaa(a)gmail.com, jjohnstn(a)redhat.com, lef(a)fedoraproject.org, mat.booth(a)redhat.com, rgrunber(a)redhat.com Target Milestone: --- Classification: Fedora Description of problem: Eclipse neither updating plugins automatically, nor able to update manually. Version-Release number of selected component (if applicable): Eclipse Platform Version: 2018-12 (4.10) Build id: X20181211-1457 How reproducible: Steps to Reproduce: 1. Try updating PDT plugin manually from http://download.eclipse.org/tools/pdt/updates/latest 2. 3. Actual results: Installation has encounter a problem. An error occurred while installing the items session context was:(profile=SDKProfile, phase=org.eclipse.equinox.internal.p2.engine.phases.Install, operand=null --> [R]org.apache.lucene.core 3.6.2, action=org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.InstallBundleAction). The artifact file for osgi.bundle,org.apache.lucene.core,3.6.2 was not found. Expected results: Eclipse Update Additional info: Started after recent Eclipse Update I also got following error: java.lang.Exception at org.eclipse.ui.internal.EditorReference.createErrorPart(EditorReference.java:343) at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:324) at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.createPart(CompatibilityPart.java:305) at org.eclipse.ui.internal.e4.compatibility.CompatibilityEditor.createPart(CompatibilityEditor.java:66) at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.create(CompatibilityPart.java:343) 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:498) at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:58) at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:1001) at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:966) at org.eclipse.e4.core.internal.di.InjectorImpl.internalInject(InjectorImpl.java:139) at org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:411) at org.eclipse.e4.core.internal.di.InjectorImpl.make(InjectorImpl.java:333) at org.eclipse.e4.core.contexts.ContextInjectionFactory.make(ContextInjectionFactory.java:193) at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.createFromBundle(ReflectionContributionFactory.java:108) at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.doCreate(ReflectionContributionFactory.java:77) at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.create(ReflectionContributionFactory.java:59) at org.eclipse.e4.ui.workbench.renderers.swt.ContributedPartRenderer.createWidget(ContributedPartRenderer.java:132) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createWidget(PartRenderingEngine.java:1015) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:675) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:781) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$0(PartRenderingEngine.java:752) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$2.run(PartRenderingEngine.java:746) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:730) at org.eclipse.e4.ui.workbench.renderers.swt.StackRenderer.showTab(StackRenderer.java:1295) at org.eclipse.e4.ui.workbench.renderers.swt.LazyStackRenderer.postProcess(LazyStackRenderer.java:105) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:693) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:781) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$0(PartRenderingEngine.java:752) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$2.run(PartRenderingEngine.java:746) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:730) at org.eclipse.e4.ui.workbench.renderers.swt.SWTPartRenderer.processContents(SWTPartRenderer.java:72) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:689) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$1.run(PartRenderingEngine.java:560) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:544) at org.eclipse.e4.ui.workbench.renderers.swt.ElementReferenceRenderer.createWidget(ElementReferenceRenderer.java:73) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createWidget(PartRenderingEngine.java:1015) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:675) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:781) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$0(PartRenderingEngine.java:752) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$2.run(PartRenderingEngine.java:746) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:730) at org.eclipse.e4.ui.workbench.renderers.swt.SWTPartRenderer.processContents(SWTPartRenderer.java:72) at org.eclipse.e4.ui.workbench.renderers.swt.SashRenderer.processContents(SashRenderer.java:140) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:689) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:781) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$0(PartRenderingEngine.java:752) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$2.run(PartRenderingEngine.java:746) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:730) at org.eclipse.e4.ui.workbench.renderers.swt.SWTPartRenderer.processContents(SWTPartRenderer.java:72) at org.eclipse.e4.ui.workbench.renderers.swt.SashRenderer.processContents(SashRenderer.java:140) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:689) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:781) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$0(PartRenderingEngine.java:752) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$2.run(PartRenderingEngine.java:746) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:730) at org.eclipse.e4.ui.workbench.renderers.swt.SWTPartRenderer.processContents(SWTPartRenderer.java:72) at org.eclipse.e4.ui.workbench.renderers.swt.SashRenderer.processContents(SashRenderer.java:140) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:689) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:781) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$0(PartRenderingEngine.java:752) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$2.run(PartRenderingEngine.java:746) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:730) at org.eclipse.e4.ui.workbench.renderers.swt.SWTPartRenderer.processContents(SWTPartRenderer.java:72) at org.eclipse.e4.ui.workbench.renderers.swt.PerspectiveRenderer.processContents(PerspectiveRenderer.java:51) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:689) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:781) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$0(PartRenderingEngine.java:752) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$2.run(PartRenderingEngine.java:746) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:730) at org.eclipse.e4.ui.workbench.renderers.swt.PerspectiveStackRenderer.showTab(PerspectiveStackRenderer.java:82) at org.eclipse.e4.ui.workbench.renderers.swt.LazyStackRenderer.postProcess(LazyStackRenderer.java:105) at org.eclipse.e4.ui.workbench.renderers.swt.PerspectiveStackRenderer.postProcess(PerspectiveStackRenderer.java:64) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:693) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:781) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$0(PartRenderingEngine.java:752) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$2.run(PartRenderingEngine.java:746) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:730) at org.eclipse.e4.ui.workbench.renderers.swt.SWTPartRenderer.processContents(SWTPartRenderer.java:72) at org.eclipse.e4.ui.workbench.renderers.swt.SashRenderer.processContents(SashRenderer.java:140) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:689) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:781) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$0(PartRenderingEngine.java:752) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$2.run(PartRenderingEngine.java:746) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:730) at org.eclipse.e4.ui.workbench.renderers.swt.SWTPartRenderer.processContents(SWTPartRenderer.java:72) at org.eclipse.e4.ui.workbench.renderers.swt.WBWRenderer.processContents(WBWRenderer.java:665) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:689) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:781) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$0(PartRenderingEngine.java:752) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$2.run(PartRenderingEngine.java:746) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:730) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1099) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:339) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1062) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156) at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:636) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:339) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:563) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:151) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:155) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:203) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:137) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:107) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:255) 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:498) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:659) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:595) at org.eclipse.equinox.launcher.Main.run(Main.java:1501) at org.eclipse.equinox.launcher.Main.main(Main.java:1474) -- You are receiving this mail because: You are on the CC list for the bug.

1 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

eclipse-sig June 2019