eclipse-sig August 2020

eclipse-sig@lists.stg.fedoraproject.org

1 participants
56 discussions

[Bug 1831160] New: eclipse - unable to change perspective
by bugzilla＠redhat.com 04 Sep '20

04 Sep '20

https://bugzilla.redhat.com/show_bug.cgi?id=1831160 Bug ID: 1831160 Summary: eclipse - unable to change perspective Product: Fedora Version: 32 Hardware: x86_64 OS: Linux Status: NEW Component: eclipse Severity: urgent Assignee: mat.booth(a)redhat.com Reporter: peljasz(a)yahoo.co.uk 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: An internal error occurred during: "Compute launch button tooltip". org/eclipse/debug/internal/ui/stringsubstitution/SelectedResourceManager Version-Release number of selected component (if applicable): eclipse-platform-4.14-5.fc32.x86_64 How reproducible: $ eclipse -clean Does not help 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.

1 1

[Bug 1853110] New: Unable to run any java program in Eclipse
by bugzilla＠redhat.com 04 Sep '20

04 Sep '20

https://bugzilla.redhat.com/show_bug.cgi?id=1853110 Bug ID: 1853110 Summary: Unable to run any java program in Eclipse Product: Fedora Version: 32 Hardware: x86_64 OS: Linux Status: NEW Component: eclipse Severity: high Assignee: mat.booth(a)redhat.com Reporter: plehal(a)lehal.net 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: Unable to launch any java program in eclipse. Even exporting the java program in any format does not work. Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. Try running any program 2. 3. Actual results: Program run fails with the following error dialog: An internal error occurred during: "Creating console for /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.252.b09-1.fc32.x86_64/bin/java (Jul 1, 2020, 9:52:24 PM)". java.nio.ByteBuffer.flip()Ljava/nio/ByteBuffer; Expected results: Program should run. Additional info: uname output :Linux fed32.xxxxxx.com 5.6.19-300.fc32.x86_64 #1 SMP Wed Jun 17 16:10:48 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1735117] New: eclipse-color-theme: FTBFS in Fedora rawhide/f31
by bugzilla＠redhat.com 04 Sep '20

04 Sep '20

https://bugzilla.redhat.com/show_bug.cgi?id=1735117 Bug ID: 1735117 Summary: eclipse-color-theme: FTBFS in Fedora rawhide/f31 Product: Fedora Version: rawhide Status: NEW Component: eclipse-color-theme Assignee: mat.booth(a)redhat.com Reporter: releng(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: eclipse-sig(a)lists.fedoraproject.org, java-sig-commits(a)lists.fedoraproject.org, mat.booth(a)redhat.com, mefoster(a)gmail.com Blocks: 1732841 Target Milestone: --- Classification: Fedora eclipse-color-theme failed to build from source in Fedora rawhide/f31 https://koji.fedoraproject.org/koji/taskinfo?taskID=36632908 For details on the mass rebuild see: https://fedoraproject.org/wiki/Fedora_31_Mass_Rebuild Please fix eclipse-color-theme at your earliest convenience and set the bug's status to ASSIGNED when you start fixing it. If the bug remains in NEW state for 8 weeks, eclipse-color-theme will be orphaned. Before branching of Fedora 32, eclipse-color-theme will be retired, if it still fails to build. For more details on the FTBFS policy, please visit: https://fedoraproject.org/wiki/Fails_to_build_from_source Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1732841 [Bug 1732841] (F31FTBFS) - Fedora 31 FTBFS Tracker -- You are receiving this mail because: You are on the CC list for the bug.

1 21

[Bug 1799301] New: eclipse-egit-github: FTBFS in Fedora rawhide/f32
by bugzilla＠redhat.com 04 Sep '20

04 Sep '20

https://bugzilla.redhat.com/show_bug.cgi?id=1799301 Bug ID: 1799301 Summary: eclipse-egit-github: FTBFS in Fedora rawhide/f32 Product: Fedora Version: rawhide Status: NEW Component: eclipse-egit-github Assignee: mat.booth(a)redhat.com Reporter: releng(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: akurtako(a)redhat.com, eclipse-sig(a)lists.fedoraproject.org, mat.booth(a)redhat.com Blocks: 1750908 (F32FTBFS) Target Milestone: --- Classification: Fedora eclipse-egit-github failed to build from source in Fedora rawhide/f32 https://koji.fedoraproject.org/koji/taskinfo?taskID=41316804 For details on the mass rebuild see: https://fedoraproject.org/wiki/Fedora_32_Mass_Rebuild Please fix eclipse-egit-github at your earliest convenience and set the bug's status to ASSIGNED when you start fixing it. If the bug remains in NEW state for 8 weeks, eclipse-egit-github will be orphaned. Before branching of Fedora 33, eclipse-egit-github will be retired, if it still fails to build. For more details on the FTBFS policy, please visit: https://fedoraproject.org/wiki/Fails_to_build_from_source Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1750908 [Bug 1750908] Fedora 32 FTBFS Tracker -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Bug 1799309] New: eclipse-subclipse: FTBFS in Fedora rawhide/f32
by bugzilla＠redhat.com 03 Sep '20

03 Sep '20

https://bugzilla.redhat.com/show_bug.cgi?id=1799309 Bug ID: 1799309 Summary: eclipse-subclipse: FTBFS in Fedora rawhide/f32 Product: Fedora Version: rawhide Status: NEW Component: eclipse-subclipse Assignee: mat.booth(a)redhat.com Reporter: releng(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: eclipse-sig(a)lists.fedoraproject.org, krzysztof.daniel(a)gmail.com, mat.booth(a)redhat.com Blocks: 1750908 (F32FTBFS) Target Milestone: --- Classification: Fedora eclipse-subclipse failed to build from source in Fedora rawhide/f32 https://koji.fedoraproject.org/koji/taskinfo?taskID=41316861 For details on the mass rebuild see: https://fedoraproject.org/wiki/Fedora_32_Mass_Rebuild Please fix eclipse-subclipse at your earliest convenience and set the bug's status to ASSIGNED when you start fixing it. If the bug remains in NEW state for 8 weeks, eclipse-subclipse will be orphaned. Before branching of Fedora 33, eclipse-subclipse will be retired, if it still fails to build. For more details on the FTBFS policy, please visit: https://fedoraproject.org/wiki/Fails_to_build_from_source Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1750908 [Bug 1750908] Fedora 32 FTBFS Tracker -- You are receiving this mail because: You are on the CC list for the bug.

1 20

[Bug 1735162] New: eclipse-subclipse: FTBFS in Fedora rawhide/f31
by bugzilla＠redhat.com 03 Sep '20

03 Sep '20

https://bugzilla.redhat.com/show_bug.cgi?id=1735162 Bug ID: 1735162 Summary: eclipse-subclipse: FTBFS in Fedora rawhide/f31 Product: Fedora Version: rawhide Status: NEW Component: eclipse-subclipse Assignee: mat.booth(a)redhat.com Reporter: releng(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: eclipse-sig(a)lists.fedoraproject.org, krzysztof.daniel(a)gmail.com, mat.booth(a)redhat.com, robert(a)marcanoonline.com Blocks: 1732841 Target Milestone: --- Classification: Fedora eclipse-subclipse failed to build from source in Fedora rawhide/f31 https://koji.fedoraproject.org/koji/taskinfo?taskID=36633209 For details on the mass rebuild see: https://fedoraproject.org/wiki/Fedora_31_Mass_Rebuild Please fix eclipse-subclipse at your earliest convenience and set the bug's status to ASSIGNED when you start fixing it. If the bug remains in NEW state for 8 weeks, eclipse-subclipse will be orphaned. Before branching of Fedora 32, eclipse-subclipse will be retired, if it still fails to build. For more details on the FTBFS policy, please visit: https://fedoraproject.org/wiki/Fails_to_build_from_source Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1732841 [Bug 1732841] (F31FTBFS) - Fedora 31 FTBFS Tracker -- You are receiving this mail because: You are on the CC list for the bug.

1 29

[Bug 1864683] New: CVE-2019-17638 jetty: double release of resouce can lead to information disclosure [fedora-all]
by bugzilla＠redhat.com 31 Aug '20

31 Aug '20

https://bugzilla.redhat.com/show_bug.cgi?id=1864683 Bug ID: 1864683 Summary: CVE-2019-17638 jetty: double release of resouce can lead to information disclosure [fedora-all] Product: Fedora Version: 32 Status: NEW Component: jetty Keywords: Security, SecurityTracking Severity: medium Priority: medium Assignee: mat.booth(a)redhat.com Reporter: gsuckevi(a)redhat.com 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 This is an automatically created tracking bug! It was created to ensure that one or more security vulnerabilities are fixed in affected versions of fedora-all. For comments that are specific to the vulnerability please use bugs filed against the "Security Response" product referenced in the "Blocks" field. For more information see: http://fedoraproject.org/wiki/Security/TrackingBugs When submitting as an update, use the fedpkg template provided in the next comment(s). This will include the bug IDs of this tracking bug as well as the relevant top-level CVE bugs. Please also mention the CVE IDs being fixed in the RPM changelog and the fedpkg commit message. NOTE: this issue affects multiple supported versions of Fedora. While only one tracking bug has been filed, please correct all affected versions at the same time. If you need to fix the versions independent of each other, you may clone this bug as appropriate. -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1800991] New: cannot upgrade eclipse because of eclipse-usage
by bugzilla＠redhat.com 28 Aug '20

28 Aug '20

https://bugzilla.redhat.com/show_bug.cgi?id=1800991 Bug ID: 1800991 Summary: cannot upgrade eclipse because of eclipse-usage Product: Fedora Version: 31 Status: NEW Component: eclipse-usage Assignee: extras-orphan(a)fedoraproject.org Reporter: listes.00(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: eclipse-sig(a)lists.fedoraproject.org, extras-orphan(a)fedoraproject.org, mat.booth(a)redhat.com Target Milestone: --- Classification: Fedora Description of problem: Cannot update eclipse, because eclipse-usage cannot find a dependency. Not sure if it is because of the obsoletes eclipse-epp-logging <= 2.0.8-4 Version-Release number of selected component (if applicable): eclipse-usage-4.11.0-1.fc31.noarch eclipse-epp-logging-2.0.7-8.fc31.noarch Informations: Problème 1: package eclipse-usage-4.11.0-1.fc31.noarch requires osgi(org.eclipse.epp.logging.aeri.core), but none of the providers can be installed - package eclipse-usage-4.11.0-1.fc31.noarch requires osgi(org.eclipse.epp.logging.aeri.ide), but none of the providers can be installed - package eclipse-platform-1:4.14-5.fc31.x86_64 obsoletes eclipse-epp-logging <= 2.0.8-4 provided by eclipse-epp-logging-2.0.7-8.fc31.noarch - cannot install the best update candidate for package eclipse-usage-4.11.0-1.fc31.noarch - cannot install the best update candidate for package eclipse-abrt-0.0.3-9.fc31.noarch Problème 2: problem with installed package eclipse-usage-4.11.0-1.fc31.noarch - package eclipse-usage-4.11.0-1.fc31.noarch requires osgi(org.eclipse.epp.logging.aeri.core), but none of the providers can be installed - package eclipse-usage-4.11.0-1.fc31.noarch requires osgi(org.eclipse.epp.logging.aeri.ide), but none of the providers can be installed - package eclipse-platform-1:4.14-5.fc31.x86_64 obsoletes eclipse-epp-logging <= 2.0.8-4 provided by eclipse-epp-logging-2.0.7-8.fc31.noarch - cannot install the best update candidate for package eclipse-epp-logging-2.0.7-8.fc31.noarch -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1800970] New: dnf update of eclipse-usage-4.11.0-1.fc31.noarch fails
by bugzilla＠redhat.com 28 Aug '20

28 Aug '20

https://bugzilla.redhat.com/show_bug.cgi?id=1800970 Bug ID: 1800970 Summary: dnf update of eclipse-usage-4.11.0-1.fc31.noarch fails Product: Fedora Version: 31 Hardware: x86_64 OS: Linux Status: NEW Component: eclipse-usage Severity: medium Assignee: extras-orphan(a)fedoraproject.org Reporter: colin.barker07(a)btinternet.com QA Contact: extras-qa(a)fedoraproject.org CC: eclipse-sig(a)lists.fedoraproject.org, extras-orphan(a)fedoraproject.org, mat.booth(a)redhat.com Target Milestone: --- Classification: Fedora Created attachment 1661970 --> https://bugzilla.redhat.com/attachment.cgi?id=1661970&action=edit output of rpm -qa Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1.run 'dnf update' 2. 3. Actual results: Problem 1: package eclipse-usage-4.11.0-1.fc31.noarch requires osgi(org.eclipse.epp.logging.aeri.core), but none of the providers can be installed - package eclipse-usage-4.11.0-1.fc31.noarch requires osgi(org.eclipse.epp.logging.aeri.ide), but none of the providers can be installed - package eclipse-platform-1:4.14-5.fc31.x86_64 obsoletes eclipse-epp-logging <= 2.0.8-4 provided by eclipse-epp-logging-2.0.7-8.fc31.noarch - cannot install the best update candidate for package eclipse-usage-4.11.0-1.fc31.noarch - cannot install the best update candidate for package eclipse-abrt-0.0.3-9.fc31.noarch - package eclipse-epp-logging-2.0.8-1.module_f31+6165+9b01e00c.noarch is filtered out by modular filtering - package eclipse-epp-logging-2.0.8-2.module_f31+6519+12cd0b27.noarch is filtered out by modular filtering Problem 2: problem with installed package eclipse-usage-4.11.0-1.fc31.noarch - package eclipse-usage-4.11.0-1.fc31.noarch requires osgi(org.eclipse.epp.logging.aeri.core), but none of the providers can be installed - package eclipse-usage-4.11.0-1.fc31.noarch requires osgi(org.eclipse.epp.logging.aeri.ide), but none of the providers can be installed - package eclipse-platform-1:4.14-5.fc31.x86_64 obsoletes eclipse-epp-logging <= 2.0.8-4 provided by eclipse-epp-logging-2.0.7-8.fc31.noarch - cannot install the best update candidate for package eclipse-epp-logging-2.0.7-8.fc31.noarch - package eclipse-epp-logging-2.0.8-1.module_f31+6165+9b01e00c.noarch is filtered out by modular filtering - package eclipse-epp-logging-2.0.8-2.module_f31+6519+12cd0b27.noarch is filtered out by modular filtering Expected results: dnf update to complete with no dependency errors Additional info: output of rpm -qa attached as package.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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

eclipse-sig August 2020